Short answer: Drop the "CircleCI → Trigger Pipeline" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Project Slug project_slug | string | Required | Format: gh/org/repo or bb/org/repo |
Branch branch | string | Optional | Branch to run the pipeline on |
Tag tag | string | Optional | Git tag to run the pipeline on (alternative to branch) |
Pipeline Parameters (JSON) parameters | string | Optional | Custom parameters defined in your .circleci/config.yml |
{"project_slug": "e.g. gh/acme-corp/my-project","branch": "e.g. main","tag": "e.g. v1.2.3","parameters": "{\"deploy_env\": \"staging\"}"}
{"id": "abc-123-def","state": "created","number": 42,"created_at": "2025-01-15T12:00:00.000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.