MightyAutomation API

01Getting started & authentication

The MightyAutomation API is project-scoped: every request acts on the project your API key belongs to. There is no project parameter on any route — the project is resolved from the key itself, so a key can never address another tenant.

All endpoints are served over HTTPS at base URL:

https://mightyautomation.com

Getting an API key

1. Sign in to MightyAutomation and open your project.
2. Go to Integrations → Zapier & other tools → Set up.
3. Click Generate Zapier key and copy it — it is shown once. Keys look like mva_zapier_….

Authenticating requests

Send the key as a Bearer token on every request:

curl https://mightyautomation.com/api/agent/me \
  -H "Authorization: Bearer mva_zapier_YOUR_KEY"

Errors & limits

• Errors return { "ok": false, "error": "<code>" } — 401 invalid_api_key, 403 insufficient_scope, 429 rate_limited.
• Rate limit: ~60 requests/minute per key.
• Validate any key with GET /api/agent/me — it returns the bound project name.

02Contacts

Create, search, and update CRM contacts. The upsert matches on email (case-insensitive); tags are merged, never replaced, and notes are appended.

Example — upsert a lead

curl -X POST https://mightyautomation.com/api/agent/contacts \
  -H "Authorization: Bearer mva_zapier_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jane@example.com",
    "first_name": "Jane",
    "last_name": "Doe",
    "phone": "+15551234567",
    "company": "Acme Inc",
    "tags": ["inbound-lead"],
    "notes": "Came in via Zapier"
  }'

→ { "ok": true, "created": true, "contact_id": "…", "events": ["contact_created"] }

03Leads & pipeline

Search leads with CRM filters and read the project's pipeline stages (needed for valid pipeline_stage values and the Stage Changed trigger).

04Events & REST-hook webhooks

MightyAutomation records a project-scoped event feed for everything that matters in the CRM and forms. Subscribe an HTTPS endpoint and we POST each event to it as it happens — this is the contract the native Zapier app uses for its triggers.

Event types

contact_createdtag_addedentered_stagelifecycle_changedform_submittedactivity_loggedappointment_bookedappointment_rescheduledappointment_cancelledappointment_completedappointment_no_showcall_completedcall_outcome

Delivery payload

Each delivery POSTs one event object: id, type, occurred_at, contact (expanded contact), and data (event-specific fields). Any 2xx is a success; subscriptions that fail repeatedly are quarantined automatically.

05Automations & scheduling

06Files & media

Import a remote file (e.g. an image or document URL from Notion, a form tool, or an email attachment) into the project's Media Assets.

07Inbound webhooks

For tools that can only send data — Zapier's Webhooks by Zapier, Make, a form backend, or a custom app — each project can mint named inbound webhook URLs from Integrations → Custom Webhooks. No API key needed: the token in the URL is the credential.

Example — Zapier "Webhooks by Zapier → POST" to a custom webhook

curl -X POST https://mightyautomation.com/api/hooks/wk_your_token_here \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jane@example.com",
    "first_name": "Jane",
    "phone": "+15551234567",
    "plan": "annual"
  }'

→ { "ok": true, "detail": "created contact 5f1b…" }
   (field_mapping on the hook can rename any payload keys first)

08Connect with Zapier (no code)

The native Mighty Automation app on Zapier wraps this API — no URLs or JSON needed:

1. In Zapier, create a Zap and search for Mighty Automation.
2. Paste your mva_zapier_… key when asked to connect an account.
3. Triggers: New Contact, Contact Tagged, Form Submitted, Pipeline Stage Changed, Appointment Booked.
4. Actions: Create or Update Contact, Add Tag, Add Note, Enroll in Automation, Import File.
5. Search: Find Contact (with find-or-create).

Endpoints the Zapier app uses

Every operation in the app maps to the public API surface documented above — nothing private or unpublished:

Example — instant trigger lifecycle

# Subscribe (when the Zap turns on)
POST https://mightyautomation.com/api/agent/hooks
{ "event_type": "appointment_booked", "target_url": "https://hooks.zapier.com/…" }
→ { "ok": true, "id": "sub_…" }

# We then POST each event to the target URL as it happens:
{
  "id": "evt_…",
  "type": "appointment_booked",
  "occurred_at": "2026-01-20T16:00:00Z",
  "contact": { "email": "jane@example.com", "first_name": "Jane", … },
  "data": {
    "title": "Discovery Call",
    "scheduled_at": "2026-01-20T16:00:00Z",
    "meeting_url": "https://meet.google.com/abc-defg"
  }
}

Example — Enroll Contact in Automation

POST https://mightyautomation.com/api/agent/enroll
{ "automation_id": "a1b2…", "email": "jane@example.com" }
→ { "ok": true, "status": "succeeded", "run_id": "r_…" }

Example — Find Contact (search)

GET https://mightyautomation.com/api/agent/contacts?email=jane%40example.com
→ { "ok": true, "contacts": [ { "id": "c8b2…", "email": "jane@example.com", … } ] }

09Machine-readable spec

The full API is described as OpenAPI 3 at GET /api/agent/openapi.json — feed it to any OpenAPI-aware tool, AI agent, or integration copilot to discover every pathway programmatically.

Questions: support@mightyautomation.com.