Automations API — event-driven workflow rules

Automations let you wire ManticScore events to external actions without writing code. Each automation has a trigger — something that happened inside ManticScore — and an action, which is something to do in a connected integration. When research finishes, post a Slack summary. When a signal is detected, create a Linear issue. When a Forge PR is created, send an email. You can use shorthand actions for common tasks or the composio.execute action to invoke any of 1000+ Composio tools with templated arguments.

List automations

curl "https://api.manticscore.com/automations" \
  -H "Authorization: Bearer <token>"

200 response

{
  "automations": [
    {
      "id": "a1b2c3d4-...",
      "trigger": "research_completed",
      "action": "slack.post",
      "toolkit": "slack",
      "config": {
        "channel": "C01234567",
        "format": "summary"
      },
      "enabled": true,
      "created_at": "2026-04-10T10:00:00Z",
      "updated_at": "2026-04-10T10:00:00Z"
    }
  ]
}

automations

object[]

Show automation properties

string

Automation UUID.

trigger

string

Event that fires this automation.

action

string

Action to execute when the trigger fires.

toolkit

string

Integration toolkit the action runs through.

config

object

Toolkit-specific configuration for the action.

enabled

boolean

Whether the automation is active.

Create an automation

trigger

string

required

The ManticScore event that fires this automation. One of:

research_completed — a market or feature research run finishes
build_graph_completed — a build graph is ready
signal_detected — a new competitive signal is detected
forge_pr_created — a Forge coding run creates a GitHub PR
brief_ready — a product brief finishes generating

action

string

required

What to do when the trigger fires. Shorthand actions:

slack.post — post a message to a Slack channel
linear.create_issues — create Linear issues from build nodes
jira.create_issues — create Jira issues from build nodes
notion.export — export content to a Notion page
gmail.send — send an email
apns.push — send a user-visible push notification to your iOS devices, with template-substituted title and body
apns.push_silent — send a background wake push to your iOS devices; the runner auto-augments the payload from the triggering event context
composio.execute — run any Composio tool (see below)

toolkit

string

required

The integration toolkit for this action: slack, linear, jira, notion, gmail, apns, or github.

config

object

required

Toolkit-specific configuration. For shorthand actions, supply channel IDs, team IDs, etc. For composio.execute, supply tool_slug and arguments with template variables.

enabled

boolean

default:"true"

Whether this automation is active immediately on creation.

curl -X POST https://api.manticscore.com/automations \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "trigger": "research_completed",
    "action": "slack.post",
    "toolkit": "slack",
    "config": {"channel": "C01234567", "format": "summary"},
    "enabled": true
  }'

201 response

{
  "id": "a1b2c3d4-...",
  "trigger": "research_completed",
  "action": "slack.post",
  "toolkit": "slack",
  "config": {"channel": "C01234567", "format": "summary"},
  "enabled": true,
  "created_at": "2026-04-18T10:00:00Z",
  "updated_at": "2026-04-18T10:00:00Z"
}

Template variables for composio.execute

When using composio.execute, your arguments values can include {{...}} template variables. The automation runner substitutes these with values from the triggering event at runtime.

Variable	Available on trigger	Value
`{{research.idea}}`	`research_completed`	The product idea text.
`{{build.title}}`	`build_graph_completed`	Title of the completed build graph.
`{{signal.company_name}}`	`signal_detected`	Display name of the company that generated the signal.
`{{signal.title}}`	`signal_detected`	Short headline of the signal.
`{{signal.summary}}`	`signal_detected`	One-paragraph signal summary.

Combine template variables with any Composio action slug to build custom automation flows — for example, creating a Jira ticket with the signal summary in the description, or posting a Notion page with the build graph title.

APNS push actions

apns.push and apns.push_silent deliver to all push tokens registered for the authenticated user via POST /push-tokens. Both actions ride the same retry and durability path as slack.post and linear.create_issues — APNS is a first-class action substrate, not a side path.

config.title

string

User-visible alert title for apns.push. Supports the same {{...}} template variables as composio.execute.

config.body

string

User-visible alert body for apns.push. Supports {{...}} template variables.

apns.push_silent does not take a title or body. The runner auto-augments a background-wake payload from the triggering event context, which iOS clients can use to refresh state without showing a notification.

Update an automation

Accepts any subset of fields. This is a sparse merge — only the fields you provide are changed. To update a single key inside config, send just that key inside the config object.

trigger

string

New trigger event.

action

string

New action.

toolkit

string

New toolkit.

config

object

Config fields to merge. Keys not provided are preserved.

enabled

boolean

Enable or disable the automation.

curl -X PATCH "https://api.manticscore.com/automations/a1b2c3d4-..." \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}'

Returns the full updated automation row on 200. Returns 400 if no fields are provided.

Delete an automation

curl -X DELETE "https://api.manticscore.com/automations/a1b2c3d4-..." \
  -H "Authorization: Bearer <token>"

Returns 204 No Content on success.

Agent autonomy

Control how much latitude the AI agent has when taking actions on your behalf. Autonomy settings apply across automations and any proactive agent actions in the chat.

autonomy_level

string

One of:

suggest — the agent proposes an action and waits for your tap to confirm
confirm — the agent shows a confirmation prompt before executing
auto — the agent acts immediately without asking

auto_actions

string[]

List of specific actions the agent can take in auto mode even if autonomy_level is suggest or confirm. Supported values: slack.post, notion.export, linear.create_issues, jira.create_issues, gmail.send, apns.push, apns.push_silent, github.create_pr.

curl -X PATCH https://api.manticscore.com/profile/agent-config \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "autonomy_level": "confirm",
    "auto_actions": ["slack.post", "notion.export"]
  }'

200 response

{
  "autonomy_level": "confirm",
  "auto_actions": ["slack.post", "notion.export"]
}

Returns the full agent_config object on 200. Returns 422 if autonomy_level is not one of the valid values.

auto_actions overrides autonomy_level for the listed actions. In the example above, Slack posts and Notion exports happen automatically even though the global level is confirm.

Spawned agents

Spawned agents are open-ended, goal-driven automations the chat agent creates inline via the spawn_agent tool. They live in the same automations table and are returned alongside trigger-action automations from GET /automations — you can tell them apart by inspecting the action field (agent.run) and the agent-specific columns described below.

goal

string

Natural-language description of what the agent should do on each run. The agent re-reads this prompt every time it fires and uses Composio to discover whichever tools it needs. Example: Every weekday at 9am, summarize Linear issues created the day before and post to #engineering on Slack.

schedule_cron

string

When the agent runs. One of:

A standard 5-field cron expression — for example 0 9 * * 1-5 (every weekday at 9am).
An ISO 8601 interval — for example PT1H (every hour).
An event sentinel — on:research_completed, on:signal_detected, on:forge_pr_created, on:build_graph_completed, or on:brief_ready.
null for one-shot agents that fire once and disable themselves.

next_run_at

string

ISO 8601 timestamp of the next scheduled run, computed from schedule_cron after each successful execution.

last_run_at

string

ISO 8601 timestamp of the most recent execution, or null if the agent has not yet fired.

last_status

string

Outcome of the most recent run. Common values: completed, failed, skipped.

run_history

object[]

Bounded log of recent runs (most recent first). Each entry includes a timestamp, status, and a short summary of what the agent did or why it failed.

integration_overrides

object

Optional per-agent overrides for integration preferences — for example, force a specific Slack channel for this agent without changing the global default.

spawned_in_session_id

string

Chat session UUID the agent was spawned from. Cron-triggered runs publish their results back into this session so the user sees agent activity in the same thread.

Spawned agents share the same automations row shape as trigger-action automations — PATCH /automations/{id} with {"enabled": false} pauses an agent, and DELETE /automations/{id} removes it permanently. The chat agent’s update_agent tool is a higher-level wrapper around the same endpoints that also accepts plain-language edit instructions.

Overview

Projects & Research

Build & Forge

Intelligence & Chat

Integrations & Ship

Automations API — event-driven workflow rules

List automations

Create an automation

Template variables for composio.execute

APNS push actions

Update an automation

Delete an automation

Agent autonomy

Spawned agents

Overview

Projects & Research

Build & Forge

Intelligence & Chat

Integrations & Ship

Documentation Index

​List automations

​Create an automation

​Template variables for composio.execute

​APNS push actions

​Update an automation

​Delete an automation

​Agent autonomy

​Spawned agents

List automations

Create an automation

Template variables for composio.execute

APNS push actions

Update an automation

Delete an automation

Agent autonomy

Spawned agents