Sync customers
When a contact is created in GetResponse, create or update the customer in Fera.
Google for Startups AcceleratorHow 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.
GetResponse Explore GetResponse →
TriggersFires when a new lead or contact is captured in GetResponse.
Fires when a contact enters an automation in GetResponse.
Fires when a field on a contact changes in GetResponse.
Fires when a contact unsubscribes in GetResponse.
Creates or updates a contact in GetResponse.
Adds a contact to a workflow or campaign in GetResponse.
Sends an email or message to a contact via GetResponse.
Changes a contact's tags in GetResponse.
More Fera + GetResponse workflows
See all Fera + GetResponse integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Sync customers” between Fera and GetResponse?
Yes — describe it in the box above and Knit's Integrations Agent researches Fera and GetResponse'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 a campaign send a review request?
Yes. When a contact reaches a stage or tag in GetResponse, Fera can send a review request.
Can reviewers be segmented?
When a review arrives in Fera, the contact in GetResponse can be tagged by rating for follow-up campaigns.