Connections
Yarla works best when the assistant is not an island: appointments in your calendar, summaries in your CRM, a message in Slack. This overview shows, per category, what is available and which article to read next.
Native actions
Actions are things the assistant does before, during or after a conversation. You create them on an assistant's Tasks tab, under Actions, with Add new.
| Connection | What it does | Article |
|---|---|---|
| Sends an email after the conversation with the summary, transcript or custom variables, to the addresses you enter, not to the caller. | Send email & SMS after a call | |
| SMS | Sends a text message from your own number after the conversation, for example a confirmation to the caller. | Send email & SMS after a call |
| HTTP request | Calls a URL of your choice: before the call (fetch context, inbound phone calls only), during the call (look something up) or after the call (push data). This is the foundation of every webhook. | HTTP request action |
| Google Sheets | Looks up rows in a spreadsheet during the call or appends a row after the call, without code. | Google Sheets action |
| After the call, sends a Meta template to a verified team number, never to the caller. The assistant must have WhatsApp connected. | ||
| CRM (HubSpot, Pipedrive) | Looks the caller up in your CRM before the call, and logs a note with the contact and a deal after it. You connect the CRM first by signing in. | HubSpot and Pipedrive |
Slack, Airtable and Baserow are not in that menu. An existing action of that type keeps working; for anything new, use an HTTP request (see Ecosystem via HTTP).
Look up during a call
These two are not under Actions, but on the same Tasks tab, under Look up during a call.
| Connection | What it does | Article |
|---|---|---|
| Live web search | Lets the assistant look up current information on the web during the call, on top of what is under Knowledge. You can limit it with Allowed domains. | Knowledge |
| Stora | During the call, looks up which storage units are free at a site, and looks up a booking by its id, on every channel. A booking is only read when it carries the number the customer proved, by caller ID or a code. You fill in the Stora base URL and the Stora token. | — |
Calendars
| Connection | What it does | Article |
|---|---|---|
| Built-in calendar | You manage services, durations and availability inside Yarla; the assistant books directly. | Appointments |
| Google Calendar and Microsoft 365 | With the built-in calendar, the assistant checks one or more calendars per service for availability and adds the appointment. Online services get a Meet or Teams link (Teams only with a work account). You connect by signing in. | Appointments |
| Cal.com | Connect a Cal.com event type with an API key; the assistant books through Cal.com, including on chat. It cannot reschedule or cancel there. | Appointments |
| eTermin | Slots, booking, reschedule and cancel, including on chat. | Appointments |
Channels
| Channel | What it does | Article |
|---|---|---|
| Phone & SMS | A new number, a forwarded or ported existing number, or a SIP trunk, on which the assistant answers calls. On a number with SMS it also replies to text messages. | Connect a phone number |
| The same assistant answers WhatsApp messages on your business number. Included in Business, Pro and Enterprise. | ||
| Webchat | A chat widget on your website or a hosted chat page. | Webchat |
Ecosystem via HTTP
Yarla does not need a separate connector per tool. Anything that can receive a webhook can be connected with an HTTP request, and with Make or n8n you need no code at all.
| Tool | How | Article |
|---|---|---|
| Make | The Custom webhook module receives the after-call data; Webhook response returns customer context before the call. | Make & n8n recipes |
| n8n | The Webhook node receives, the Respond to Webhook node answers. | Make & n8n recipes |
| Zapier | Catch Hook for after-call data. | Make & n8n recipes |
| Slack | One message per conversation via Make or n8n, or directly to a Slack incoming webhook as an HTTP request. | Make & n8n recipes, HTTP request action |
| HubSpot and Pipedrive | Connected directly with a CRM task. For anything else, such as a ticket, use Make or n8n or an HTTP request to their API. | HubSpot and Pipedrive, Make & n8n recipes |
| Notion | Create a database row via Make or n8n, or directly through the Notion API. | HTTP request action |
| Airtable and Baserow | Look up or append rows with an HTTP request directly to their API. | HTTP request action |
For developers
| Component | What it does | Article |
|---|---|---|
| API | Read conversations, requests, contacts and appointments, create contacts, update requests and contacts, and start outbound calls from your own software. Outbound calls are included in Business, Pro and Enterprise. | API |
| Webhooks | Receive data at three moments (before, during and after the call). Every request that is not a GET is signed. | Webhooks |
| Event webhooks | For your whole account: a message for every ended conversation, new request and booked or cancelled appointment, with test-send and resend. Enterprise. | Event webhooks |
Which one do I need?
- You just want to stay informed. An Email or SMS action after the call. No technical work needed.
- You want every conversation in a spreadsheet. The Google Sheets action.
- You work with HubSpot or Pipedrive. Connect the CRM and add a CRM task: the assistant recognises callers and logs every conversation.
- You want data in another CRM, Slack or another SaaS tool. An HTTP request to Make or n8n, and build the connection to your tool there.
- You want the assistant to recognise the caller. An inbound webhook (pre-call) that returns customer details. This only works on inbound phone calls.
- You want the assistant to look something up during the call, such as an order status or an open invoice. A webhook during the call, or Google Sheets if the data lives in a spreadsheet.
- You want appointments straight into your calendar. The built-in calendar, optionally with Google Calendar or Microsoft 365, or Cal.com or eTermin.
- You are building software yourself. The API to read and to dial out, webhooks to have data pushed to you.
Start small
Begin with an Email action after the call. Once you are happy with what the summaries contain, replace that action with an HTTP request to your own system. If you leave the Body template empty, you receive the summary and transcript as JSON, together with the other variables.
Manage connections
Under Settings → Connections you manage the keys your assistants and services use. An Editor or Admin can open the page. A Viewer does not see it.
- Connected shows, for each key, the name, the Kind, who uses it (Used by, with a link to that assistant or service) and when it was created. Below that, On for your assistants and services says what is in use now. Email, SMS and the built-in calendar do not count as a connection.
- Replace puts a new value on the same connection, so everything keeps working. It can take up to 5 minutes to apply everywhere. You do not replace a calendar: use Reconnect for that.
- Delete only works once nothing uses the connection any more.
- Add connection stores a new key: you choose a Name and the Kind, and paste the Value. The value is never shown again. You can also paste a key directly into the field on an action or channel. You do not add a calendar here; you connect it by signing in.
- Available shows what you can connect. Each row links with Set up to where you arrange it. You connect a calendar right there with Connect a calendar, and HubSpot and Pipedrive with Connect.
- API keys, Webhook secret and Event webhooks are for admins only, see API, Webhooks and Event webhooks.
- Request a connection is for a service that is not listed. Fill in a Name and, under What should it do?, what you need, and choose Send request. Your request stays on this page.