Zapier
Start a Zap on a new lead or ticket, a ticket that changed, a conversation that ended or an answer, and let a Zap ask your agent, teach it or work on a ticket.
ChatterLab's Zapier integration starts a Zap when something happens in your workspace: a visitor leaves their contact details or opens a ticket, a ticket changes, a conversation ends, or your agent answers. The lead, the ticket, the conversation or the answer can then go on to a CRM, a spreadsheet, your team's chat or any other app Zapier connects. A Zap can also act in ChatterLab: ask your agent a question, teach it something, or set a ticket's status and add a note. It is part of Studio and up: it connects with an API key and works through webhooks.
Note. The integration is not in Zapier's app directory yet. You add it to your Zapier account through our invite link, and it works the same way.
Adding it to Zapier
- Open our invite link while you are signed in to Zapier, and accept the invitation. ChatterLab is then among the apps you can choose in the Zap editor.
- In ChatterLab, make a key for it: in Workspace settings, under Developers, on the API keys card, press New key and choose Manage under What it may do. Turning a Zap on adds a webhook, and only a key that may manage can do that.
Making a Zap
- In Zapier, make a Zap and choose ChatterLab as its trigger, with one of the events under The triggers.
- Connect your account with the key. With a key for the whole workspace, Zapier names the connection after your workspace.
- Under Agent, choose the agent whose events should start the Zap. Left empty, every agent's do, including agents you add later.
- Test the trigger. Zapier shows up to three recent examples from the agent you chose, or from your workspace's oldest agent when you chose none. These are real ones, with what visitors wrote, except for Ticket Updated, which shows a made-up ticket: what changed and how is only told when it happens.
- Add the steps that should follow and turn the Zap on. A webhook to hooks.zapier.com appears on the Webhooks card in Workspace settings, Developers.
The triggers
| Trigger | Starts the Zap when | The Zap receives |
|---|---|---|
| New Lead | A visitor leaves their details in the chat's form | The lead |
| New Ticket | A visitor hands a question to your team, or a mail to the agent becomes a ticket | The ticket |
| Ticket Updated | A ticket's status changes, your team replies, a note is added, or the visitor replies by e-mail | The ticket, with what changed and which way the change came |
| Conversation Ended | A conversation has been quiet for 30 minutes | The conversation, every message in it |
| New Answer | A visitor receives an answer, in the chat, by e-mail or on WhatsApp | The answer, with the visitor's question |
| Weak Answer | An answer counts as weak, as on the Overview | The answer and the question, with why it is weak |
Each receives what the matching webhook sends, in the shape the API returns it. The events on the webhooks page say exactly when each is sent and what it holds.
- Conversation Ended comes again, whole, each time the visitor comes back and the conversation goes quiet again. Keep it by its Conversation ID and replace what you had. Conversations in the Playground or over the API never start it, nor one in which the visitor only said hello.
- New Answer starts the Zap once for every answer, and each run is a task in your Zapier plan: a busy agent can use hundreds a day. Answers in the Playground or over the API never start it.
- Weak Answer follows the Overview's rule, so it includes answers over the API. Its test step shows the agent's weakest answers of the last 30 days rather than the most recent ones.
- Ticket Updated has a switch, Include changes made with an API key, which is off. See Loops.
The actions
| Action | What it does |
|---|---|
| Ask Agent | Asks the agent a question and gives back its answer, its confidence, its grounding and the sources it drew on |
| Add Text Source | Adds a text with a title to what the agent knows |
| Add Q&A Source | Adds a question with its answer, up to 500 and 10,000 characters |
| Set Ticket Status | Sets a ticket to open, waiting on the customer or solved. Nothing is mailed to the visitor |
| Add Ticket Note | Adds a note of up to 10,000 characters, which only your team sees. Nothing is mailed to the visitor |
Every action asks for the agent. The ticket actions list that agent's tickets, the latest activity first, or take a Ticket ID from an earlier step. A trigger that watches every agent does not tell the action which agent it was, so a Zap that acts on a trigger's ticket needs the same agent chosen in both.
- Ask Agent is a question like any other: it costs credits exactly as one in the chat does, and so does testing the step in the Zap editor, which asks for real. It appears in Activity as a conversation over the API. To go on with a conversation, give it the Conversation ID of an earlier Ask Agent step.
- Add Text Source and Add Q&A Source are pending until the agent has learned them, which takes seconds to a minute. A text that would take the agent past its plan's storage allowance is refused.
- Setting the status a ticket already has changes nothing.
Loops
A Zap that acts on its own trigger can start itself again, and again, using tasks and credits each time.
- A change made with an API key is how Zapier changes a ticket, so Ticket Updated skips such changes unless you switch on Include changes made with an API key. Leave it off for a Zap that adds a note or sets a status on updated tickets.
- Weak answers to questions asked with an API key are sent, as the Overview counts them, so Weak Answer skips them unless you switch on Include answers to questions asked with an API key. Leave it off for a Zap that asks the agent again on a weak answer: the agent likely answers weakly again.
- Ask Agent never starts New Answer or Conversation Ended: the conversation it asks in is always one the API began. Given the Conversation ID of a visitor's conversation, from New Answer or Conversation Ended, it starts a new conversation instead of going on with theirs.
Warning. Turn a Zap off in Zapier as soon as you see it running more often than visitors write. How many, and loops on the webhooks page says more.
What happens next
- Each event starts the Zap within seconds. Conversation Ended can come a few minutes after the 30 quiet minutes are up, since we look every few minutes.
- Zapier checks that each delivery was signed by ChatterLab, and ignores one that was not.
- Now and then one event starts the Zap twice, for instance when Zapier took longer than 5 seconds to answer. The Lead ID, Ticket ID, Conversation ID or Answer Message ID is the same both times.
- Turning the Zap off deletes its webhook. Each Zap that is on holds one of the workspace's 25 webhooks, shared with the ones you add yourself.
- Deleting the key does not stop a Zap that is on: its webhook keeps sending, and a delivery needs no key. Turn the Zap off first, or delete its webhook on the Webhooks card. Zapier asks you to connect again the next time it needs the key, such as when you test the trigger, run an action or turn the Zap off.
- Zapier, a company in the United States, receives what your Zap is given: with Conversation Ended, New Answer and Weak Answer, what visitors wrote. Once there, it is in your care, under Zapier's terms.