Update records from contact changes
When a contact is updated in SATORI, update the matching record in Kintone.
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.
SATORI Explore SATORI →
TriggersFires when a new lead or contact is captured in SATORI.
Fires when a contact enters an automation in SATORI.
Fires when a field on a contact changes in SATORI.
Fires when a contact unsubscribes in SATORI.
Creates or updates a contact in SATORI.
Adds a contact to a workflow or campaign in SATORI.
Sends an email or message to a contact via SATORI.
Changes a contact's tags in SATORI.
Kintone Explore Kintone →
TriggersFires when a new record is added to an app built in Kintone.
Fires when a record changes in an Kintone app.
Fires when a record is deleted in an Kintone app.
Adds a new record to an app built in Kintone.
Updates an existing record in an Kintone app.
Removes a record from an Kintone app.
More SATORI + Kintone workflows
See all SATORI + Kintone integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Update records from contact changes” between SATORI and Kintone?
Yes — describe it in the box above and Knit's Integrations Agent researches SATORI and Kintone'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 record add a contact to a campaign?
Yes. When a record is created in Kintone, SATORI can add the contact to a list or start a sequence.
Can marketing activity update records?
When a contact is added or engages in SATORI, the matching record in Kintone can be updated.