Chain Workflows with Hooks

Set up a hook that automatically triggers a follow-up workflow whenever another workflow finishes — no manual handoff needed.

Internally still called a playbook.

What You'll Use

Feature	Purpose
Hooks	Event-driven triggers that fire when something happens
Workflows	The two workflows you'll chain together

Step 1: Create the First Workflow

Start with a simple workflow that produces an output.

1. Go to Workflows in the sidebar and click New Workflow.

Field	Value
Name	Daily Metrics Snapshot
Description	Summarizes key metrics into a report artifact
Default Agent	Any agent

2. Add a single freeform instruction:

Review the latest data available in the workspace and create a short metrics summary artifact covering revenue, active users, and support ticket volume. If exact data is not available, note what's missing.

3. Set Auto-Approve to Yes so it runs without intervention.

Step 2: Create the Follow-Up Workflow

This workflow will run automatically after the first one completes.

1. Create another workflow:

Field	Value
Name	Post Metrics Summary
Description	Reads the latest metrics artifact and posts a summary
Default Agent	Any agent

2. Add a freeform instruction:

Find the most recent "Daily Metrics Snapshot" artifact. Write a 3-bullet summary of the key takeaways. Save it as a new note artifact titled "Metrics Highlights — [today's date]".

TIP

If you have a Slack connection, change the instruction to post the summary to a channel instead. This turns the chain into a fully automated daily briefing pipeline.

Step 3: Create the Hook

Now connect the two workflows with an event-driven hook.

1. Go to Hooks in the sidebar and click New Hook.

Field	Value
Name	Chain: Metrics → Summary
Event	run.completed
Action	Run Workflow
Target Workflow	Post Metrics Summary

2. Add a filter so it only fires for the right workflow:

   • Filter: Source workflow is "Daily Metrics Snapshot"

3. Save the hook.

INFO

The run.completed event fires whenever any workflow finishes successfully. The filter ensures your hook only triggers for the specific workflow you want. Other available events include run.failed, artifact.created, todo.created, and more.

Step 4: Test the Chain

1. Open Daily Metrics Snapshot and click Run.
2. Watch it execute on the Jobs page (/jobs).
3. When it completes, the hook automatically triggers Post Metrics Summary.
4. A second run appears on the Jobs page — started by the hook, not by you.
5. When both finish, check Artifacts for both the snapshot and the highlights note.

Step 5: Add a Schedule (Optional)

To make this fully automatic:

1. Open Daily Metrics Snapshot and set a schedule:
   • Schedule: Every weekday at 8:00 AM (0 8 * * 1-5)
2. The chain now runs itself — the schedule triggers the first workflow, and the hook triggers the second.

WARNING

If the follow-up workflow has approval steps, its run will pause and wait for your review. Set up notifications so you don't miss pending approvals in a fully automated chain.

What to Try Next

• Triggers & Schedules — All trigger types and event reference
• Scheduling Automation — Cron expressions, timezone settings
• Monitoring Runs — Track chained runs and debug failures