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

> ## Agent Instructions
> For API operations, fetch https://gateway.firsttouch.ai/api/public/openapi.json for the complete input/output schemas, internal references, and x-mcp-annotations. Endpoint Markdown intentionally omits generated schema fragments. Select /api/public/tools/<tool_name> using the exact underscore-separated name. Send requests to https://gateway.firsttouch.ai; the canonical document currently omits servers. Start at https://docs.firsttouch.com/api-reference/agent-start.md.

# Add Contact Action

> Append exactly one action to an existing single-contact sequence created through create_contact_sequence or the earlier Dynamic Actions tool.

<details>
<summary><strong>Detailed usage guidance</strong></summary>
<ul>
<li>Requires its exact enrollmentId.</li>
<li>Never creates a new enrollment and cannot append to ordinary reusable Flow Plan enrollments.</li>
<li>Only in-progress and completed sequences can be extended; completed sequences reopen automatically.</li>
<li>Pending, failed, and canceled sequences are rejected.</li>
<li>This adds a step to the sequence, not an unconditional immediate send: its position, delay, branch, and approval determine when it can run.</li>
<li>Reuse the enrollment-wide email inbox and LinkedIn sender; another sender requires create_contact_sequence.</li>
<li>For email, subjectType is required: new_thread needs subject; reply needs a prior email on the selected branch and inherits its subject.</li>
<li>Use action.appendTarget for an existing LinkedIn connection&#39;s accepted or timeout branch.</li>
<li>Read get_guide with topic=workflow_selection before choosing this workflow, then topic=dynamic_actions before writing.</li>
<li>First call get_current_user and require authenticated access and granted dynamic_actions:write for the active team.</li>
<li>Members can create only self-owned sequences, use only their own sender/inbox or task assignment, and extend or cancel only their own sequences.</li>
<li>Sequences containing another member&#39;s actions remain admin-only.</li>
<li>Ownership is permanent and set only during creation.</li>
<li>Admins use find_contact_data with known identities unless verified enrichment was already returned.</li>
<li>Members use supplied verified contact data and their own find_mcp_enrollment results; do not call restricted lookup tools.</li>
<li>Provide final content using exactly one typed action.</li>
<li>Approval defaults to enabled; action.isHumanApprovalRequired=false is allowed only when the customer explicitly requests it.</li>
<li>Actions may send messages, consume FirstTouch credits, or create user tasks.</li>
<li>Execution follows approval, delay, branch, account readiness, and sender capability checks.</li>
<li>Use the returned enrollmentId with enrollment inspection and cancellation tools; flowPlanId is not permission to modify the shared flow structure.</li>
</ul>
</details>



## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.firsttouch.com/llms.txt).


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