Intro to automations
What you need to know about automations
Overview 
Automations help your team save time by automating repetitive tasks, minimize human error, and can be used to design a delightful client experience. For example, you can set up built-in automations where if a client logs in the first time, they're automatically assigned an intake form and default files and folders are uploaded. Then, in Zapier or Make, once the form is submitted you can update custom field values to update client information.
Ways of setting up automations
Setup method | Use case |
|---|---|
Built-in | We currently have 3 built-in automations in the Automations app in the sidebar: 1. Assign a contract when a client logs in for the first time 2. Assign a form when a client logs in for the first time 3. Upload files and folders when a company/client is created You can read more in the Copilot Automations section here. Additionally, welcome messages are automated by default and can be customized on the Messages App settings pages. |
Zapier | Most popular no-code option with many templates to choose from and largest collection of integration. |
Make | No-code option with more flexibility and customizability. |
API | Requires developer resources but gives maximum control and flexibility. |
Frequently Asked Questions
To create your API key, you'll want to go to Settings > API in the Copilot Dashboard.
Click Create key. In the dialog, label your key.
Click Create key. In the next dialog, you'll see your generated key.
Be sure to copy the key and paste it somewhere secure on your local device - once the dialog is closed, you will not have access to copy the key again. You can always revoke the current key and create a new one, however.
Your API Key is needed to perform automations with Zapier, Make, or to use our API directly.
If you are an admin user, you can create webhooks on the Settings > API page.
To create a webhook, click New webhook in the Webhooks section. Label your webhook, paste your endpoint URL, and select which events to send to the webhook.
Note: Make only supports one webhook per event per scenario. If using a Make webhook for a Copilot trigger, be sure to only send the event that corresponds to the trigger.