Advanced / Sandbox

Internal beta — not released yet

The Automation API is an internal beta and is not released yet. Its endpoints and payloads are not final and may change or be withdrawn at any time without notice.

These two endpoints are the execution backends of specific automation actions — the machinery an automation uses under the hood when it runs. You rarely call them directly; they exist so an automation can call another automation, or hand out a weblink, as part of its own run.

Endpoint	Backs the action
`POST /v1/automation/{automation_id}/trigger`	Call automation — `current_record_call_automation`, `collected_records_call_automation`
`POST /v1/automation/weblink/generate`	Generate weblink — `current_record_generate_automation_weblink`

See Actions for those action types.

These behave differently from the rest of the resource

Because they are the sandbox execution backends, they don't follow the resource-wide conventions:

They accept either a user API key or an automation API key (the rest of the resource is user-key only).
They report problems as a 400 (validation error), not the 404 collapse the CRUD endpoints use.

Both cost 1x base credits. Only the call-automation endpoint is asynchronous — it answers 202 with an empty body and no run ID, so you poll the Automation Run API. The weblink-generate endpoint is synchronous: it answers 201 with the minted weblink inline; only the eventual click-triggered run is asynchronous.

Call an automation

POSThttps://api.tapeapp.com/v1/automation/{automation_id}/trigger

Fires an automation on a record — the mechanism behind the Call automation actions. The target automation must have an automation_called trigger. Its trigger filter is applied (a record that doesn't match produces no run).

Body Parameters

Parameter	Type	Required	Description
`trigger_on_record_id`	`integer`	yes	The record to run the automation on.
`triggered_by_record_id`	`integer`	no	The record that initiated the call.
`triggered_by_workflow_def_id`	`integer`	no	The automation that initiated the call.
`trigger_with_arguments`	`object`	no	Arguments passed into the run, per the automation's declared input variables.
`is_manual_run`	`boolean`	no	Defaults to `false`.
`is_simulation`	`boolean`	no	Defaults to `false`.

➡️      Request
curl -X POST https://api.tapeapp.com/v1/automation/88/trigger \
  -u user_key_replace_with_your_api_key: \
  -H "Content-Type: application/json" \
  --data '{ "trigger_on_record_id": 5001 }'

Answers 202 with an empty body {} — like manual-run, it is asynchronous and returns no run ID; poll the Automation Run API for the result. A 400 is returned if the body is malformed, the automation or record does not exist or you can't access it, or the record does not belong to the automation's app.

A 202 means the call was accepted, not that a run was created. The call still answers 202 while silently producing no run when the target does not fire: its trigger is not automation_called, its trigger filter rejects the record, or it is paused or broken (automations are created paused — activate the target first). Confirm the run through the Automation Run API.

Deprecated alias

The legacy path POST /v1/workflow/{automation_id}/trigger is kept as a deprecated alias for older integrations. Use /v1/automation/….

Generate a weblink

POSThttps://api.tapeapp.com/v1/automation/weblink/generate

Mints a public weblink that, when clicked, fires a weblink_clicked automation on a record — the mechanism behind the Generate weblink action. Requires that you can view the referenced record.

Body Parameters

Parameter	Type	Required	Description
`trigger_workflow_def_id`	`integer`	yes	The `weblink_clicked` automation the weblink fires.
`trigger_on_record_id`	`integer`	yes	The record the weblink is scoped to.
`triggered_by_record_id`	`integer`	no	The record that initiated generation.
`triggered_by_workflow_def_id`	`integer`	no	The automation that initiated generation.
`trigger_with_arguments`	`object`	no	Arguments carried by the weblink into the run.
`expiration_type`	`string`	no	One of `NEVER`, `ONE_DAY`, `ONE_WEEK`, `ONE_MONTH`, `ONE_YEAR`.
`expire_after_first_click`	`boolean`	no	Invalidate the weblink after its first click.
`is_manual_run`	`boolean`	no	Defaults to `false`.
`is_simulation`	`boolean`	no	Defaults to `false`.

➡️      Request
curl -X POST https://api.tapeapp.com/v1/automation/weblink/generate \
  -u user_key_replace_with_your_api_key: \
  -H "Content-Type: application/json" \
  --data '{
    "trigger_workflow_def_id": 91,
    "trigger_on_record_id": 5001,
    "expiration_type": "ONE_WEEK"
  }'

⬅️      Response
{
  "trigger_token": "wl_9f8c…",
  "trigger_client_url": "https://app.tapeapp.com/weblink/wl_9f8c…"
}

Answers 201. A 400 is returned if the body is malformed or the target automation is not a weblink_clicked automation. Always send trigger_workflow_def_id and trigger_on_record_id — the endpoint needs the automation to fire and the record to scope to.

`expiration_type` here ≠ the action's config key

The expiration_type param above (UPPER-CASE NEVER / ONE_DAY / …) is the shape of this endpoint's body. When you instead configure the backing current_record_generate_automation_weblink action, the config key is different — weblink_expiration — and its tokens are lower-case (never, one_day, one_week, one_month, one_year; the action also has on_click). Copying the endpoint's key/casing into an action config writes the wrong field.

Deprecated alias

The legacy path POST /v1/workflow/weblink/generate is kept as a deprecated alias. Use /v1/automation/….

Internal beta — not released yet

These behave differently from the rest of the resource

Call an automation​

Deprecated alias

Generate a weblink​

expiration_type here ≠ the action's config key

Deprecated alias

Call an automation

Generate a weblink

`expiration_type` here ≠ the action's config key