With the Simplesat app in Zapier, a new response can start a Zap. A Zap can also send a survey, add or update customers and team members, or look up a response. For example, you could post negative ratings to a Slack channel, add a Trello card or a Google Sheets row for every response, or send a survey when a task is completed in Asana.
Simplesat built the app and maintains it. It works through the Simplesat API, so you connect it with an API key. API keys management covers creating and managing keys, and the Simplesat API documentation covers the API itself.
Before you start
You need a Simplesat API key. API keys are available on every Simplesat plan. To create one, you need the Owner or Admin role, or a custom role with Access API key.
Pick the kind of key before you create it. A Full access key works for everything in the app. A Custom key works with the New Feedback trigger whatever scopes you give it, but each action and search needs its own scope:
Action or search | Scope it needs |
Send Event-Based Email Survey | Responses: Write, and Surveys: Read for the list of surveys |
Upsert Customer | Customers: Write |
Upsert Team Member | Team members: Write |
Find Customer | Customers: Read |
Find Team Member | Team members: Read |
Find Response | Responses: Read |
Connect Simplesat to Zapier
In Simplesat, go to Admin → API keys, create a key and copy it. You only get to see the key once, at the moment you create it.
In Zapier, add a Simplesat trigger or action to a Zap.
When Zapier asks you to connect Simplesat, paste the key into API key.
Zapier names the connection after your Simplesat workspace. Each key belongs to one workspace, so to use another workspace, connect again with that workspace's key.
Start a Zap when a response arrives
Choose New Feedback as your trigger. It starts your Zap for each new response from every survey in your workspace, about five minutes after the response arrives. Withheld and spam responses don't start it, and neither do responses created through the API.
To act on only some responses, add a Zapier Filter step after the trigger. For example, let the Zap continue only when the sentiment is negative, or only for one survey name.
Each response comes into Zapier with fields you can use in later steps. They include the survey, the rating with its label and sentiment, the comment, the customer's name, email and company, the team member, the ticket ID and subject, the response's tags, and a link to the response. You also get:
A field for each ticket and team member custom attribute in your workspace.
A field for every question of every survey, named Survey name / Question text / Field name.
For surveys sent through Zendesk, ConnectWise or Autotask, fields from those tools, such as the Zendesk group and assignee or the ConnectWise board.
When you test the trigger, Zapier pulls in your most recent response, from whichever survey it came from. That response is only a sample. Once the Zap is on, it runs for every survey.
Tip: If you'd rather receive each response at a Zapier webhook URL, go to the Simplesat Tools page under Integrations. The options that start with Send data to API endpoint post each new or updated response to a URL.
Actions and searches
Name | What it does |
Send Event-Based Email Survey | Sends one of your event-based email surveys to a customer |
Upsert Customer | Creates a customer, or updates the one with the same email |
Upsert Team Member | Creates a team member, or updates the one with the same email |
Find Customer | Finds a customer by ID |
Find Team Member | Finds a team member by ID |
Find Response | Finds a response by ID |
Send Event-Based Email Survey lets you pick from your event-based email surveys. Customer email is required. You can also fill in the customer's name and company, the team member's ID, name and email, the ticket ID and subject, and custom attributes for the customer, the team member and the ticket. Write custom attributes as JSON, for example {"Plan": "Pro"}. To learn more about event-based email surveys, see Direct email surveys.
Upsert Customer requires an email. You can also give it a name, a company, an external ID, custom attributes as JSON, and tags separated by commas.
Upsert Team Member requires an email. You can also give it a name, an external ID and custom attributes.
Troubleshooting
Zapier asks for an account key
Zapier needs an API key. Create one on Admin → API keys and paste it in. If your workspace has a Legacy account key, that works too.
Zapier says my API key is invalid
First check that you copied the whole key. Then make sure the key still exists on Admin → API keys, because a deleted key stops working right away. If the key is gone, create a new one and connect again.
My Zap's trigger works but an action fails
With a Custom key, each action needs its own scope, even though the trigger works with any. Add the scope from the table in Before you start to your key, or connect with a Full access key. A scope you add takes effect right away, so you don't need to reconnect Zapier.
A new survey isn't starting my Zap
New Feedback covers every survey, new ones included, so you don't need to change anything in Zapier. Responses take about five minutes to reach your Zap. If nothing arrives after that, check that the Zap is on and that a Filter step isn't stopping it. Responses created through the API don't start a Zap, and withheld or spam responses don't either.
Only one survey shows when I test the trigger
Zapier tests the trigger with your most recent response, so you see only one survey. Once the Zap is on, it runs for every survey.
FAQ
Can I start a Zap for only some surveys or ratings?
Yes. Add a Filter step after New Feedback and filter on something like the survey name or the sentiment.
Do responses I create through the API start a Zap?
No. Responses created through the API don't start New Feedback.
Can I send a survey from Zapier?
Yes. Send Event-Based Email Survey sends one of your event-based email surveys to the customer email you give it.