Make the next step explicit.

Make the next step explicit

A workflow describes when a repeatable process should start and which steps follow. Its trigger, inputs and review points make the sequence easier to understand before it is used.

Consider a customer record marked Follow up. A proposed sequence can read the record, prepare a draft and pause before sending anything. Naming the trigger and the review checkpoint helps you spot missing context before deciding what should happen next.

Put it to work

Interview-stage preparation

Explore a sequence that starts when a candidate reaches Interview and prepares questions for review.

Draft review

Inspect the steps between marking content ready for Review and preparing editorial notes.

Vendor renewal review

Set out the information and decision checkpoint for a renewal entering its review window.

Inspect a sequence before activating anything

Explore workflows, then follow the example there:

1. Choose a workflow and review its fictional trigger, proposed sequence and human-review checkpoint.
2. Approve the example, then edit its context and steps and save the definition.
3. Use Activate demo or Deactivate demo to change its local status, then review a simulated run.
4. Inspect the sample decision and saved steps. The simulation stops at a review checkpoint without external action.

How it fits in your workspace

• Tables for record context — Explore the fields behind statuses and next actions.
• Skills for reusable methods — Write the procedure followed during a piece of work.
• Integrations for access boundaries — Inspect fictional service permissions before any authorization.

Common questions

How are TulipFarm workflows different from skills?

A workflow sets when a process starts and the steps that follow, including where it waits for a person to review. A skill holds a reusable method for doing a piece of work. In the Explore tour, sample workflows, skills and tables are separate and not connected.

Does activating a workflow in the Explore tour schedule it?

No. Activate demo only changes a status saved in your browser. It doesn't register a trigger, watch for table changes or schedule anything. Run simulation shows a fixed, fictional result and stops at the review step without calling outside services.

Workflow triggers, activation and results are simulated locally. No events are subscribed to and no messages are sent.