Skip to main content

Triggers

A trigger is the starting point of every blueprint -- it defines what event causes your automation to run.

Why triggers matter​

Without a trigger, a blueprint is just a plan sitting idle. The trigger is the "when" of your automation:

  • When an API call comes in, do something
  • When a contact attribute changes, do something

Every blueprint must have exactly one trigger node.

Trigger types​

REST API Trigger​

The REST API trigger starts a workflow when an external system sends an HTTP request to Orqio.

How it works:

  1. You add a REST API trigger to your blueprint
  2. Orqio generates a unique webhook URL for that blueprint
  3. Your application or service sends a POST request to that URL
  4. The workflow starts, and the request payload is available to downstream nodes

Common use cases:

  • Your backend sends an event when a new order is placed
  • A third-party service (like Stripe or Shopify) sends a webhook
  • A scheduled job in your system triggers a daily report

Example request:

curl -X POST "https://app.orqio.io/public/api/v1/orgs/$ORG_ID/workspaces/$WORKSPACE_ID/triggers/$TRIGGER_ID" \
  -H "x-api-key: $ORQIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"orderId": "12345", "customerEmail": "jane@example.com"}'

The JSON payload becomes available in downstream nodes through expressions.

For technical users

The trigger URL and authentication requirements are documented in the API Reference. Each trigger has a unique ID that you include in the URL path.

Attribute Change Trigger​

The attribute change trigger starts a workflow when a contact's attribute changes in Orqio.

How it works:

  1. You add an attribute change trigger to your blueprint
  2. You specify which attribute to watch (e.g., status, plan, score)
  3. Optionally, you add conditions (e.g., only trigger when status changes to active)
  4. When the attribute changes and conditions are met, the workflow starts

Common use cases:

  • Send a welcome email when a contact's status changes to active
  • Notify a sales rep when a lead's score exceeds a threshold
  • Update an external CRM when a contact's plan changes

Conditions on triggers​

Both trigger types support conditions that filter when the workflow actually runs:

  • Value match -- only trigger when the value equals something specific
  • Value change -- only trigger when the value changes from one state to another
  • Threshold -- only trigger when a numeric value crosses a boundary

Conditions help you avoid running workflows unnecessarily and keep your automations focused.

Best practices​

  • Use descriptive trigger names so your team knows what starts each blueprint
  • Set conditions to avoid unnecessary workflow runs
  • Secure your API triggers with API keys -- never expose trigger URLs publicly without authentication
  • Test triggers in staging before connecting production systems