Autopilot

CRM & salesAPI keyConnection test available

Add, update, look up and delete Autopilot contacts, and manage the contact lists they belong to, through the Autopilot v1 REST API.

OCNORA ships 8 typed Autopilot operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api2.autopilothq.com/v1 through the HTTP node with the same credential.

Before you connect Autopilot

Authentication
API key
Credential
the Autopilot API key (sent as the autopilotapikey header)the API key, or {"api_key": "…"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
Prerequisites
  • The same API key the autopilot.* action nodes use — Autopilot has one key per account and no per-scope keys, so a key that can read contacts can register REST Hooks. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Autopilot can reach.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with Autopilot

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

A sample Autopilot workflow

  1. 1
    Eventtrigger.autopilot_event
    Start a run when Autopilot fires a REST Hook (contact added, updated, unsubscribed, or moved in or out of a list or segment).
  2. 2
    Get Contactautopilot.get_contact
    Retrieve one contact record by its Autopilot id or email address.
  3. 3
    Add Contact To Listautopilot.add_contact_to_list
    Add an existing contact to a contact list. A contact already on the list comes back with not_modified set rather than as a failure.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Triggers 1

Operations 8

Autopilot questions

How does OCNORA authenticate with Autopilot?
With a stored API key credential, shaped the Autopilot API key (sent as the autopilotapikey header) or the API key, or {"api_key": "…"}. A connection test can check it when you add it.
What can I automate with Autopilot?
8 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Autopilot operation I need is not listed?
Call https://api2.autopilothq.com/v1 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Autopilot?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Autopilot calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Autopilot workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.