Moab logoMoab
Get started
Moab Docs

Channels & Sending

Connect a provider with one call, authorize it per project, and know exactly what happens between an approval and a delivered message.

A channel is a connected provider — Resend, Instantly or Lemlist for email, HeyReach for LinkedIn — plus your authorization to send through it. Those are two separate things: the credential is storage, the routing is config. A sequence is the multi-touch cadence a campaign walks a person through on top of them.

Connect a provider

curl --fail-with-body "https://moabcrm.com/api/v1/integrations" \
  -H "Authorization: Bearer $MOAB_API_KEY" \
  -H "Project-ID: $PROJECT_ID" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: acme-integrations.create-1' \
  -d "$(jq -n --arg INSTANTLY_API_KEY "$INSTANTLY_API_KEY" '{"provider":"instantly","credentials":{"api_key":$INSTANTLY_API_KEY}}')"

Use the provider registry's field names — api_key for lemlist, heyreach, instantly and resend; heyreach also takes linkedin_account_id. Credentials are write-only: accepted on create, encrypted, never echoed back. GET /integrations lists what this project has connected; a second create with the same key replays the first.

Read a campaign's cadence

List sequences — GET /api/v1/sequences

curl "https://moabcrm.com/api/v1/sequences" \
  -H "Authorization: Bearer $DASH_API_KEY" \
  -H "Project-ID: pr_zest"
Show me the sequences filtered by status
data_query {
  "collection": "sequences"
}

{
  "object": "list",
  "data": [
    {
      "object": "sequence",
      "id": "obj_123",
      "name": "name",
      "status": "status",
      "created_at": "2026-07-25T12:00:00.000Z",
      "updated_at": "2026-07-25T12:00:00.000Z"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

A sequence is a definition only. Per-person progress lives on the person (person.sequence_*), and every send, open and reply is a timeline event.

Authorizing a channel

Attaching is not authorizing. A connection attaches per project on the paused | sandbox | live ladder and starts at sandbox until an operator presses Live on it. Routing then lives in the project's configuration under moab.channels, one block per provider: presence is the enable, each sender ties an identity to its employee persona, and send_budget_per_day is your authorization — it clamps the provider's own capacity and never raises it, with 0 meaning draft-only, the default for a new sender.

How a send actually happens

There is no channel-send endpoint. A send happens only at the end of one path:

draft → approve → provider → delivered, on the provider's evidence.

Approve resolves the sender and releases the draft to the provider; the row reaches sent only when the provider confirms it. In sandbox the recipient is rewritten onto the sandbox audience first; in live the campaign agent itself must be live. Every rule on that path fails closed — an unreadable budget blocks the send rather than guessing — and delivery, refusal and engagement all land as events on the draft and its person. run_mode is a column on the project, never config, and a task run can never change its own project's mode (Control plane).

Let the agent do it

The channels skill refreshes provider status and records engagement; it never hand-rolls a provider call. integrations_list and integrations_get name which providers this project has and which operations each supports.

tasks_create { "project_id": "pr_zest", "skill_id": "channels", "run": true,
               "prompt": "Refresh channel status and record this week's engagement." }

Next: Analytics — what the sending earned.

On this page

Moab logoMoab

Ready to build? Connect an agent and go — no credit card needed to start.

Get startedSee our plans