Airtable
In Airtable every answer becomes data you can work with. Store an answer as its own record, flag the weak scores, and attach the analysis when a wave is done.
Workflows you can build with it
Each example is a workflow you can set up with an automation service, an AI assistant or your own application.
Every answer in the right field
Score, comment and date go into number, text and date fields instead of one text column. For teams that filter, group and calculate inside Airtable.
Flag the weak scores
A score of 2 or less sets the record’s status to “Needs review”, which puts it in the service team’s view. For owners who track exceptions to the end.
Keep survey waves comparable
A weekly fetch writes the running survey’s headline numbers onto the record for that wave. For research teams comparing quarter against quarter.
Link the response to its product
When the answer names a product, the workflow finds that record and sets the link. For product teams who read feedback on the product, not in a collection list.
Attach the analysis to the wave
At the end of a wave a scheduled run requests the chart export and attaches it to the analysis record. For anyone who looks for the result and the raw data in one place.
What the integration transfers
Each point is a separate example in the direction of the arrow. Configure each workflow independently and link the relevant survey for actions on an existing survey.
empirio.ai → Airtable
- One record per response, in number, select and date fields rather than text
- A link to the record for the product or the survey wave
- The chart export as an attachment on the matching analysis record
Airtable → empirio.ai
- New record in the survey table: create a survey from its fields
- Record enters the “Ready to send” view: publish the survey it belongs to
How to set it up
A select field only accepts values that already exist as options, so the first unknown answer text fails the write. A link needs a unique key the response itself carries; anonymous responses do not carry one. Renaming fields later costs more than naming them once.
