Automations
Triggers
Initiate workflows based on specific events
Introduction
Triggers are the events that start an Automation. After you turn on an Automation, Thoughtly will monitor for the event you’ve selected, then run the Automation when the event occurs. This will cause all of the Actions in the Automation to run in sequence.Integration Triggers
In addition to the default Triggers, Thoughtly also supports Integration Triggers that connect to third-party software. These Triggers allow you to start an Automation based on an event that occurs in another software application. Thoughtly supports a wide range of Integration Triggers. Some of the most popular integrations and their Triggers include:- Typeform: Start an Automation when a new form is submitted.
- Salesforce: Start an Automation when a new lead is added to Salesforce.
- HubSpot: Start an Automation when a new lead is added to HubSpot.
- GoHighLevel: Start an Automation when a new lead is added to GoHighLevel.
- Zendesk: Start an Automation when a new ticket is created in Zendesk.
Default Triggers
Thoughtly comes with a set of default Triggers that you can use to start your Automations. These are available to all users and can be used in any Automation you create.On Call Completed
Using the On Call Completed trigger, you can start an Automation every time one of your Voice Agents ends a call. This allows you to run Actions after a call ends, such as updating a record in your CRM, sending an SMS, or scheduling another call.Trigger
Outputs
dutation_ms: The duration of the call in milliseconds. This can be used to calculate the cost of the call for billing purposes.recording_url: The URL of the call recording. This can be used to store the recording in your CRM or other software.phone_number: The phone number of the caller. This can be used to save the caller in your CRM or other software.transcript: The transcript of the call. This can be used to analyze the conversation for keywords or sentiment.
Webhook
The Webhook trigger allows you to start an Automation when a webhook is received. This can be used to integrate with third-party software that supports webhooks, such as Zapier, Make, or your own custom software.
To use the Webhook trigger, you’ll need to copy the URL provided by the trigger and paste it into the software that will be sending the webhook. Once you click “Refresh” in the Thoughtly UI, the trigger will check for any new webhook payloads that have been sent.
You can use these payloads to pass data to your Voice Agents using Metadata, or other Actions in the Automation using Variables.
Authentication
To secure your webhook, you can enable Authentication on your webhook. Once enabled, your webhook endpoints will require standard authentication just like the rest of the Thoughtly API. Read more about API authentication.Inbound Call
Using the Inbound Call trigger, you can start an Automation every time a call comes in. This allows you to retrieve data from your CRM, Google Sheets, or other software, then connect the call to your Voice Agents with all the information they need to have a productive conversation.
Keep in mind that, while the Automation is running, the caller will hear a standard dial tone until the Automation is complete. The more complex the Automation, the longer the caller will be on hold.
After retrieving data or running other Actions, you can connect the call to your Voice Agents using the “Connect Call” Action. If you gathered data from other steps in the Automation, you can pass that data to your Voice Agent by using Metadata.
Recurring Schedule
The Recurring Schedule trigger allows you to set up an Automation to run at a specific time every day, week, or month. This can be used for sending out appointment reminders, making calls to new leads during business hours, or just checking in with customers on a regular basis.