Work with records
- Find recordsLocate the rows the next step needs.
- Create recordAdd new work with mapped values.
- Update recordChange one record or bulk update many.
- Delete recordRemove a record through the same controlled flow.
Automations
Turn the work you repeat into a workflow.
Choose what starts it. Connect the decisions and actions. Publish the flow, then see exactly how every run moved.
A workflow is not a hidden script.
TriggerDecideActReview01 / Start
Start from the moment that matters.
A workflow can react to the work itself, wake up on time, or listen for another system. Pick one clear trigger, then use its data everywhere downstream.
- 01
Record event
Start when a Rowkit record is created, updated, deleted, or changed in bulk. Watch specific fields when the workflow should stay quiet until something meaningful changes.
- 02
Schedule
Run once, on an interval, or on a daily, weekly, monthly, or cron schedule in the timezone you choose.
- 03
Incoming webhook
Give another system a verified endpoint that can start a Rowkit run and pass its payload into the flow.
02 / Build
Draw the logic the way the work actually moves.
Connect steps on a visual canvas. A Condition can open separate paths. For each repeats a group. Wait holds the work until the right moment. Every input can use the trigger or an earlier step.
Trigger data Bound value Published step
03 / Act
Keep the common work simple. Keep the unusual work possible.
Most flows can stay close to the records. When the process reaches outside Rowkit, use a focused communication, request, webhook response, or Code step.
Control the flow
- ConditionBranch with all, any, and not rules.
- For eachRepeat a group of steps for every item.
- WaitPause without holding a worker, then resume later.
- StopEnd a branch deliberately when no more work is needed.
Reach outside Rowkit
- Send emailCompose and send a message from workflow context.
- HTTP requestCall an external endpoint with bound inputs.
- JavaScriptUse a Code step for custom transformation logic.
- Respond to webhookReturn a controlled response to the calling system.
04 / Observe
Know what ran, what waited, and what needs attention.
Run history keeps the source, each step, every attempt, and the final outcome together. Durable waits and scheduled retries remain part of the same visible run.
Practical answers
Before you publish the first flow.
Does editing change a live workflow?
No. You work in a draft and publish a version when it is ready. A running automation stays pinned to its published graph.
What happens when a step fails?
The run records the failed step and its attempt. A retry policy can schedule another attempt with controlled backoff.
Can a workflow pause for later?
Yes. A Wait step parks the run durably, so it can resume on a timer without keeping a worker open.
Can Rowkit call another system?
Yes. Use an HTTP request, send an email, or start from and respond to an incoming webhook.
Can the team see what happened?
Yes. Run history preserves the trigger, step status, outputs, attempts, duration, and final outcome for review.
Let the system remember the next step.
Build one workflow around the handoff your team repeats most, then keep improving it as the operation changes.