CircleCI
CircleCI pipeline orchestration
CircleCI is the CI/CD platform used by engineering teams to run tests, build artifacts, and deploy on every push. Tiny Command exposes four actions, no triggers (CircleCI emits build-status webhooks per-project configured in project settings; point them at a Tiny Command webhook trigger for "deploy finished" workflows): Trigger Pipeline (start a CI run for a project, optionally on a specific branch with custom parameters that the .circleci/config.yml can branch on), Get Pipeline (status, workflows, jobs), List Pipelines (recent runs with filters), Cancel Workflow (stop an in-flight workflow — useful when a downstream check fails and you want to short-circuit the rest of the pipeline). The connection uses a CircleCI Personal API Token from User Settings → Personal API Tokens. The trigger-pipeline pattern is the common workflow shape: an external event (a Linear issue moved to "ready for staging", a manual approval in Slack) fires a Tiny Command workflow that calls Trigger Pipeline with parameters baked into the CircleCI config to control which steps run.
Do anything CircleCI can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Cancel Workflow | Stops an in-flight workflow. Useful for "downstream check failed, short-circuit the rest of the pipeline" cascading workflows or for emergency stop on accidental production deploys. |
| Get Pipeline | Returns a pipeline by ID with its workflows, jobs, and current state. The standard lookup for workflows that triggered a pipeline and need to poll for completion before proceeding. |
| List Pipelines | Returns paginated pipelines for a project with state and branch filters. Useful for "what shipped this week" reports and for CI-health monitoring workflows. |
| Trigger Pipeline | Starts a CI run with optional branch and parameter overrides. Useful for "Linear issue moved to deploy → trigger production pipeline" or "rollback requested → trigger pipeline with deploy_version=X parameter" patterns. |
Pre-built CircleCI workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect CircleCI once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every CircleCI field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the CircleCI integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect CircleCI to Tiny Command?
What CircleCI triggers does Tiny Command support?
What CircleCI actions can I run from a workflow?
Is the CircleCI integration real-time?
Do I need to write code to use CircleCI with Tiny Command?
How much does the CircleCI integration cost?
More crm & sales apps people connect.
Same category as CircleCI, ordered by how often teams pair them. Hover the carousel to pause.
Do more with CircleCI.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
