Let a new message start work in your other apps
Zapier connects to Vera.Support through our webhooks. Once it is wired up, events such as an incoming message or a new user can set off anything Zapier can reach.
This is for you if the conversations in your inbox need to reach somewhere else: a spreadsheet, a CRM, a project board, an internal alert. You do not need to write code, but you do need a Zapier account.
Step by step
Start with the ready-made app
On our cloud, use the ready-made Vera.Support Zapier app. It saves you building an integration by hand. If you would rather build your own, follow the manual route in the next steps.
Create the trigger in Zapier
Create a Zapier integration and add a trigger with the type REST Hook. Create a Zap that uses it, then copy the Webhook URL that Zapier gives you.
Paste the URL into the panel
In cloud.vera.support, open Settings > Miscellaneous > Webhooks > URL and paste the Webhook URL there. Activate webhooks, save, then reload the page.
Send a real event and test
Trigger something so there is data to look at: send a message, or create a user. Then click Test Trigger in Zapier to see what arrived.
Add a filter so the Zap is choosy
In Zapier, add a Filter step and let the Zap continue only when the variable you care about exists. For a message integration, continue only if message exists.
Settings reference
| Setting | What it does |
|---|---|
| Settings > Miscellaneous > Webhooks > URL | The Zapier Webhook URL that your events are sent to. |
| Settings > Miscellaneous > Webhooks | Where webhooks are switched on; nothing reaches Zapier until they are active and you have saved and reloaded. |
Good to know
Every webhook reaches every Zap
We send all webhooks to all of your Zaps. Without a Filter step, a Zap fires on events it was never meant to handle, so the filter matters more than it sounds.
Each webhook is a trigger
Because every one of our webhooks acts as a trigger, you have 15 or more triggers to build Zaps on.
One URL can feed several Zaps
To use more than one Zap, append the extra Zap IDs to the URL, separated by commas, like https://hooks.zapier.com/hooks/catch/10352851/bbad21f,aaaa66t/
Reload after saving
Once you have activated webhooks and saved, reload the page. Skipping the reload is a common reason the connection looks dead.
Test Trigger needs real data
Zapier shows nothing until an event has actually happened. Send a message or create a user first, then press Test Trigger.
Common questions
Do I have to build a Zapier integration myself?
What can set off a Zap?
Why does my Zap run on things that have nothing to do with it?
Where do I put the Webhook URL?
Can I connect more than one Zap at the same time?
Does this cost extra?
Ready to end the chaos?
Unify your messages, automate the repetitive questions, and turn conversations into revenue — starting today.
Get Started