Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iblueprint.ai/llms.txt

Use this file to discover all available pages before exploring further.

Triggers define how and when a blueprint runs automatically. Each trigger is attached to a specific blueprint and has a triggerType that determines the activation source — from a recurring schedule to an incoming Slack message. iBlueprint evaluates active triggers continuously and fires the associated blueprint when a trigger’s conditions are met. You can attach multiple triggers to a single blueprint.

​
Trigger types

TypeDescription
manualFired explicitly via the blueprintTriggers.fire procedure or the iBlueprint UI.
scheduledFires on a cron schedule. Supply a cron expression in config.cron.
webhookFires when an external HTTP request hits the generated webhook URL. See Webhooks.
emailFires when an email arrives at the blueprint’s inbox address.
slackFires when a specific Slack event occurs (e.g. a message in a channel).
eventFires in response to an internal iBlueprint platform event.
apiFires when called programmatically via the blueprintTriggers.fire mutation.

​
List triggers — blueprintTriggers.list

Returns all triggers configured for a blueprint. Procedure type: query (HTTP GET) Endpoint: 
GET https://api.iblueprint.ai/api/trpc/blueprintTriggers.list

​
Parameters

​
json.blueprintId
string
required
UUID of the blueprint whose triggers you want to list.

​
Response

An array of trigger objects.
​
id
string
UUID of the trigger.
​
blueprint_id
string
Blueprint this trigger is attached to.
​
trigger_type
string
One of the trigger types listed above.
​
config
object
Trigger-specific configuration. For scheduled triggers, contains cron. For webhook triggers, may contain a secret for signature verification.
​
is_active
boolean
true if the trigger is currently enabled.
​
created_by
string
UUID of the user who created the trigger.

​
Example

curl -G "https://api.iblueprint.ai/api/trpc/blueprintTriggers.list" \
  --data-urlencode 'input={"json":{"blueprintId":"3fa85f64-5717-4562-b3fc-2c963f66afa6"}}' \
  -H "Authorization: Bearer YOUR_API_KEY"

​
Create a trigger — blueprintTriggers.create

Adds a new trigger to a blueprint. Procedure type: mutation (HTTP POST) Endpoint: 
POST https://api.iblueprint.ai/api/trpc/blueprintTriggers.create
Content-Type: application/json

​
Parameters

​
json.blueprintId
string
required
UUID of the blueprint to attach the trigger to.
​
json.triggerType
string
required
The type of trigger. Accepted values: manual, scheduled, webhook, email, slack, event, api.
​
json.config
object
Trigger-specific configuration object. Defaults to {}.For a scheduled trigger, provide a cron expression:
{ "cron": "0 9 * * 1-5" }
For a webhook trigger, you can optionally provide a secret for signature verification:
{ "secret": "your-webhook-secret" }

​
Examples

curl -X POST "https://api.iblueprint.ai/api/trpc/blueprintTriggers.create" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "json": {
      "blueprintId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "triggerType": "scheduled",
      "config": {
        "cron": "0 9 * * 1-5"
      }
    }
  }'

​
Sample response

{
  "result": {
    "data": {
      "json": {
        "id": "trigger-uuid",
        "blueprint_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "trigger_type": "scheduled",
        "config": { "cron": "0 9 * * 1-5" },
        "is_active": true,
        "created_by": "user-uuid"
      }
    }
  }
}