An API is a way for other software to communicate with Tape. It can send instructions to Tape and get information back, without someone clicking through Tape’s interface.
Tape’s public API already lets scripts, integrations, and connected AI tools work with Tape. The new Automation API extends this to workflow automations.
You can now build, test, run, and manage automations through the API. The automation structure stays the same:
Trigger → Optional filters → Actions
Ways to use the Automation API
- Create automations with their trigger, filters, and actions without opening the Automation Center in Tape.
- Update automations in bulk , for example by changing the same filter condition across automations in 50 customer workspaces at once.
- Test before activation by checking and simulating an automation before taking it live.
The full automation lifecycle via API
Over the past few weeks, we’ve added the API features to cover building, running, monitoring, and improving automations:
- Connect to Tape with personal access tokens (PATs), our recommended way to give scripts, tools, and AI assistants access.
- Build and manage automations with the new Automation API.
- Inspect individual runs and their logs with the Automation Runs API.
- Track actions, successful runs, failed runs, and cancelled runs over time with the Automation Usage Report API.
Build automations with your AI assistant
Write in Claude Code or Codex what you want an automation to do, in plain language. With the Tape MCP Server, the AI can create or update the automation directly in Tape.
How to get started
Start with our Automation API documentation for the quickstart, examples, and full API reference.
New to APIs? Our Tape API guide walks you through your first requests step by step.
Beta
The Automation API is currently in beta. Endpoints, payloads, and behavior may change or be withdrawn during the beta.
We’d love your feedback. Share an idea or report an issue here: