- How to automatically send Slack messages to a channel whenever a new client is created in Harvest
- 1. Set the Harvest trigger as “Client created”
- 2. Add the “Send message” step in Slack
- 3. Activate your playbook
- Learn more about integrating with Slack and Harvest
- Related blog posts
- More how-to guides featuring Slack and Harvest
How to automatically send Slack messages to a channel whenever a new client is created in Harvest
Set the Harvest trigger as “Client created”
Once you have finished creating your playbook, the next step would be to begin with the first action. A playbook always starts with a trigger, which is responsible for detecting changes in your connected applications and responding accordingly.
Add the Harvest trigger to initiate your playbook's actions whenever a new client is created. Click "Add trigger" in your playbook and choose "Client created" from the dropdown menu under Harvest. This will allow your playbook to automatically identify newly created client profiles and trigger necessary actions.
If you still need to connect your Harvest account to Relay.app yet, a prompt will guide you through the process.
Add the “Send message” step in Slack
Integrate Slack automation into your playbook to ensure that you receive timely updates whenever a new client is created in Harvest.
Select "Add Step" and then find the "Send message" automation for Slack. Enter all the required details, including the sender's name, the Slack channel for updates, and the message body containing detailed information.
If you still need to connect your Slack account to Relay.app, you will be prompted to complete that connection. Ensure that you allow the necessary permissions for Relay.app to send messages through your Slack account.
Activate your playbook
Activating your playbook is the last step in the process. Once you turn it on, it will automatically send Slack messages to a channel whenever a new client is created in Harvest without requiring manual intervention.
To activate your playbook, click the toggle button at the header. Before activating, we recommend performing a test run of your playbook to ensure all the steps work seamlessly together.