Workflow overview
Why this workflow matters
Supports knowledge capture and document intelligence use cases.
In Grist, when I mark a row as confirmed (via a toggle): a webhook is set up to notify AlekSystem, and this workflow will create derived records in the destination table. Design decisions Confirmation-based In the source table there is a boolean column "Confirmed" that will trigger the transfer. This way there is a manual check involved & it's a conscious step to trigger the workflow. Runs once If the destination table already contains an entry, we will not re-create/update it (as it might've already been changed manually) Setup Create a boolean column Confirmed in source table Add a webhook in Grist Settings Add grist API credentials in AlekSystem Set document ID & source table ID/Name in the 'get existing' node Set docID, the destination table ID/Name - and the columns & values you want in the Create Row node
Best fit
Categories
Services
Use cases
Need another direction?