> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations

> Account-wide, event-driven workflows. Distinct from a campaign flow: an automation reacts to something happening (a reply, a tag, a booking) rather than walking a lead through a sequence.

<Info>Requires the **Automations** permission. Tools in this group are hidden from `tools/list` and refused on call when your plan does not grant it.</Info>

| Tool | Kind |
| - | - |
| [`automation_duplicate`](#automation_duplicate) | Write |
| [`automation_get`](#automation_get) | Read-only |
| [`automation_list`](#automation_list) | Read-only |
| [`automation_upsert`](#automation_upsert) | Write |

## automation\_duplicate

<Badge color="orange">Write</Badge>

Copy an automation into a new inactive draft. The copy starts inactive, so it is safe: nothing runs until `automation_upsert` sets `isActive: true`. Use it to try a change without touching the automation currently handling live events.

### Parameters

<ParamField path="automationId" type="string" required>
  Automation id, from `automation_list`.
</ParamField>

## automation\_get

<Badge color="blue">Read-only</Badge>

One automation with its full workflow graph. Read one before authoring another with `automation_upsert`: the node and edge shape is not documented anywhere else, and a hand-built graph that does not match it will not run.

### Parameters

<ParamField path="automationId" type="string" required>
  Automation id, from `automation_list`.
</ParamField>

## automation\_list

<Badge color="blue">Read-only</Badge>

Account automations — event-driven workflows that run outside any single campaign. This is also where event delivery to your own systems belongs: webhooks are deprecated and their tools are gone, so do not look for them. A campaign sequence is a different thing entirely — that is `flow_get` and `flow_set`.

*No parameters.*

## automation\_upsert

<Badge color="orange">Write</Badge>

Create an automation, or update one by passing `_id`. The `flow` graph uses the same node/edge shape as the automations builder in the web app — read an existing one with `automation_get` before authoring a new graph by hand. Setting `isActive: true` makes it run against live events, which can message real people — leave it false while drafting and get an explicit yes before activating. It replaces the whole `flow` graph rather than patching it, so pass the complete graph. It does not touch any campaign sequence (`flow_set`). There is no tool to delete an automation.

### Parameters

<ParamField path="_id" type="string">
  Omit to create a new automation.
</ParamField>

<ParamField path="title" type="string" required>
  Short label.
</ParamField>

<ParamField path="description" type="string" required>
  Longer explanatory text.
</ParamField>

<ParamField path="flow" type="object (free-form)">
  Workflow graph — nodes and edges.
</ParamField>

<ParamField path="isActive" type="boolean">
  Whether it runs. Keep false while drafting.
</ParamField>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.