Skip to main content
FirstTouch lets agents inspect and manage outbound workflows: find contacts, build Audiences and Flow Plans, add outreach steps, review tasks, and inspect results. Start by checking the current user and team, then load the guidance and operation schema for the requested workflow.

​
Choose A Connection

Use the HTTP quickstart for server integrations or MCP connection setup for an assistant. Public API keys belong to their creator and are fixed to the team selected at creation. Store credentials in a secrets manager or secure client configuration, never in prompts or documentation.

​
Load Only What You Need

  1. Read the operation catalog to find the exact tool name and endpoint page.
  2. Read the selected operation’s description, prerequisites, input schema, and response schema in the canonical OpenAPI document. The HTTP path is /api/public/tools/ followed by the exact tool name, including underscores.
  3. Read the matching get_guide topic before starting that workflow. For a broader overview of agent behavior, use the FirstTouch agent guide.
The catalog contains direct Markdown links for every operation. Use the canonical OpenAPI document to resolve schema references and inspect x-mcp-annotations. Descriptions can specify constraints that are not expressed as schema keywords. An empty response schema does not define an empty response; do not invent fields, status values, or retry guarantees where the contract leaves them unspecified.

​
Make Your First Call

Call get_current_user with {}. Follow the quickstart for complete curl and PowerShell requests and response interpretation. Then follow its read-only workflow to load a guide, page through Flow Plans, and inspect an existing plan. Check isAuthenticated, userId, teamId, permissions, and warnings before selecting resources or making changes. A successful identity check does not establish access to every operation: review the requested operation’s role, plan, sender, and credit requirements. Use get_auth_scopes for current capabilities and list_team_members when resolving a sender.

​
Choose The Workflow

These are starting points, not complete request bodies. Use the linked catalog and each operation’s schema for its required inputs. get_guide also accepts overview, which is the default topic. For example, send this body to /api/public/tools/get_guide:

​
Understand The Objects

Use returned IDs when moving between operations. Do not substitute display names for IDs. Adding an action, creating a task, approving it, and confirming execution are distinct steps.

​
Before Actions Or Credit Spend

  • Follow the operation’s prerequisites and the user’s requested scope. Resolve the contact, sender, and team before outreach.
  • For Dynamic Actions, load get_guide with topic=dynamic_actions, perform the documented contact and enrollment checks, resolve the assigned sender, and ensure the effective identity includes both first and last name. Ask for missing names instead of automatically enriching.
  • Check current costs with get_feature_costs and credit context with get_credits_usage when needed. A read operation can consume credits; a read-only annotation does not mean free.
  • Review changes and obtain any confirmation required by the workflow. Creating an approval task does not authorize completing it.
  • Preserve returned identifiers and inspect the result before reporting completion. Follow execution and recovery for pending tasks, failed imports, and ambiguous sends.