Share survey responses
When a survey response arrives in Fera, post it in Slack.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Fera Explore Fera →
TriggersFires when a customer leaves a new review in Fera.
Fires when a review is edited or answered in Fera.
Fires when a customer answers a feedback survey in Fera.
Invites a customer to leave a review with Fera.
Adds or updates a customer contact in Fera.
Posts a public reply to a review in Fera.
Slack Explore Slack →
TriggersFires when a new message is posted to a channel in Slack.
Fires when your team or a keyword is mentioned in Slack.
Fires when a new channel is created in Slack.
Fires when a new file is shared in Slack.
Posts a message to a channel in Slack.
Sends a direct message to a person in Slack.
Creates a new channel in Slack.
Adds a user to a channel in Slack.
More Fera + Slack workflows
Alert on low ratings
When a low-rated review arrives in Fera, send a message to a manager in Slack.
See details
See all Fera + Slack integrations → · Browse the full workflow library →
Common questions
Can Knit build “Share survey responses” between Fera and Slack?
Yes — describe it in the box above and Knit's Integrations Agent researches Fera and Slack's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can reviews post to a channel?
Yes. When a new review arrives in Fera, Slack can post the rating and text.
Can I route bad reviews?
Low-rated reviews from Fera can go to a separate channel or directly to a manager in Slack.