> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ironlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows · Blueprints

> Multi-step, reusable workflows. Coming soon.

<Warning>
  **Coming soon.** Workflows (working name: **Blueprints**) are in active design. Today's path for multi-step automation is a combination of [Skills](/foundry/skills/overview), [Connectors](/foundry/connectors/overview), and [Scheduled Tasks](/foundry/tasks/scheduled).
</Warning>

## What Blueprints will be

A **Blueprint** is a reusable, multi-step recipe — a sequence of model calls, connector invocations, and conditional branches packaged as a single thing you can trigger by name.

Think: *"run my **Weekly Competitor Brief** blueprint"* and Foundry executes a 4-step pipeline — crawl, summarize, score, deliver — without you having to re-orchestrate it every time.

## Examples we're prototyping

| Blueprint                   | What it does                                                                                |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| **Weekly Competitor Brief** | Crawl target sites → extract pricing/feature deltas → write a 1-page brief → post to Slack. |
| **Lead Enrichment**         | For each new lead → look up the company → score fit → append notes → update CRM.            |
| **Content Repurposer**      | Take a long-form article → produce 5 X posts + 1 LinkedIn post + a YouTube short script.    |

## How it'll differ from Skills + Tasks

* A **Skill** is an *expertise* — a way to behave.
* A **Task** is a *trigger* — when to run.
* A **Blueprint** is a *plan* — multi-step orchestration with branches and parallel steps.

## Want early access?

Tell Foundry — *"add me to the Blueprints waitlist"* — and we'll loop you in as private beta opens.

## Today's workaround

For multi-step automation right now, stack:

1. A Skill that codifies the steps as instructions.
2. The relevant Connectors so the assistant has the tools.
3. A Scheduled Task to run the prompt on a cadence.

Not as clean as Blueprints will be — but it works.

## Related

<CardGroup cols={2}>
  <Card title="Skills" icon="puzzle-piece" href="/foundry/skills/overview">
    Today's reusable behavior.
  </Card>

  <Card title="Scheduled tasks" icon="clock" href="/foundry/tasks/scheduled">
    Today's automation trigger.
  </Card>
</CardGroup>