Four triggers, three actions, one API key
A survey answer becomes a Slack message, a customer at risk becomes a task in your CRM, a new company in your CRM becomes a customer in Sightelle. No code.
When something happens in Sightelle
New survey response
Someone submitted one of your surveys. The Zap gets the score, the answers, the time and the reference you passed in the link, so the answer can return to the order or the ticket it came from. You can narrow it to one survey.
New recovery case
A low score opened a recovery case. The Zap gets the survey, the score, the due date and a link to the case. Contact details stay in Sightelle, where only your editors see them. It needs the recovery rule turned on.
Customer health declined
A customer moved to «at risk», once per change, at 08:00 your time. The Zap gets the company, the reasons and a link. It needs the customer health rule turned on.
Theme alert fired
One of your alert rules fired on a theme. The Zap gets the theme, the numbers and a link, never customer words.
When something happens elsewhere
Send feedback
A ticket, a review or a message from any tool becomes feedback in Sightelle, and from there signals and themes. Each item carries its own ID, so a Zap that runs twice does not count anything twice.
Create timeline event
A release, an outage, a price change or a campaign goes on the timeline. When a theme rises, Sightelle shows which event came before it.
Create or update customer
Keeps your customer list and ARR in step with your CRM, so feedback is linked to companies and weighted by revenue. A field the Zap leaves empty keeps its value, and a customer someone edited by hand in Sightelle is never overwritten.
One key, created by the workspace owner
Where do I get the key?
In Sightelle, under Team and access → API keys. Choose «For Zapier, Make or n8n» and the key gets exactly the permissions the triggers and actions need. Only the workspace Owner creates keys, and a key is shown once.
Where do I see what is connected?
Under each key, in the same screen: every event subscription, where it delivers (Zapier, Make, n8n) and when it last delivered. A subscription that keeps failing is paused, and you are told.
And Make or n8n?
They use the same API, without an app: a webhook module subscribes to an event, and an HTTP module calls the actions. The steps and the request bodies are in Sightelle, under API.
You choose where your data goes
Who decides what is sent?
You do. Zapier, Make or n8n run under your own account, and Sightelle delivers only to the addresses your Zaps subscribe. It is the same as a webhook you set up yourself, and the data processing agreement covers it.
What never leaves?
The contact details of a recovery case and the words of customers in an alert. Survey responses and customer health carry customer data, so they also need the key’s permission to read data.
How do I stop it?
Turn off or delete the Zap, delete the subscription under Team and access, or revoke the key. Revoking a key stops every subscription it made.
Where to find the Zapier app
Want the invitation link?
Write to us and tell us which tool your team uses.