Skip to main content

Blueprints

A blueprint is the design of an automation -- the steps, logic, and connections that define what should happen when something triggers it.

What is a blueprint?​

A blueprint is a no-code automation plan that you build visually in the Orqio editor. It defines:

  • What starts it (a trigger)
  • What happens next (a sequence of connected nodes)
  • How decisions are made (conditions, loops, and branches)

Think of a blueprint like an architect's plan for a building. The plan describes what should be built, but it isn't the building itself. Similarly, a blueprint describes an automation, but it only becomes a live process when you publish and run it.

Blueprints vs. workflows​

These two terms are closely related:

BlueprintWorkflow
What it isThe design (nodes, connections, logic)A running instance of a blueprint
AnalogyA recipeA meal being cooked
Where you edit itThe workflow builderYou don't edit a running workflow
StateDraft or PublishedRunning, Completed, or Failed

When you hit Run once or a trigger fires, Orqio creates a workflow (an execution) from your blueprint.

For more on workflows and their lifecycle, see Workflows.

What makes up a blueprint?​

A blueprint contains:

  1. A trigger -- the event that starts the automation (see Triggers)
  2. Nodes -- the individual steps (see Node Types)
  3. Connections -- the lines between nodes that define execution order
  4. Configuration -- settings on each node (see Node Configuration)

Building a blueprint​

  1. Open Workflows in the Orqio app and click Create Workflow
  2. Add a trigger node from the palette
  3. Add action and integration nodes
  4. Connect them in the order you want them to run
  5. Configure each node's settings
  6. Validate, test with Run once, and publish when ready

For the full lifecycle (drafts, publishing, validation), see Blueprint Lifecycle.

Best practices​

  • Name blueprints by business outcome, not technical details. Use send-welcome-email instead of trigger-http-sendgrid-v2.
  • Start simple. Begin with 2-3 nodes and add complexity once the basics work.
  • Build in staging first. Use your staging workspace for development and testing.
  • Keep blueprints focused. If a blueprint does too many things, split it into smaller automations.