Skip to content

Integrations

Replies go where your team already works.

Every reply stops the sequence, lands in the Unibox, and goes straight to your dialer or CRM. Handoff to Nooks, Orum and SalesFinity, sync to HubSpot and GoHighLevel, plus webhooks, an API and MCP for the rest.

Book a demoSee pricing

01Directory

Your CRM, your dialer, your automations.

Native connections where your team spends its day, and webhooks plus an API for everything else.

Launch
Available when we launch.
At launch · in validation
Built for launch, being validated against each dialer's API.
Planned
On the roadmap. Not built yet.

A · 1 integration

Messaging infrastructure

The provider layer every line runs on.

  • Infrastructure
    LoopMessage

    Carries every message on your dedicated lines: iMessage first, with SMS and WhatsApp on the same number.

B · 4 integrations

CRM

One-way push: contacts, conversations and reply status.

  • Launch
    HubSpot

    Upserts the contact, logs the conversation as activity, and sets the status on a positive reply.

  • Launch
    GoHighLevel

    Upserts the contact and logs every message, so the client's pipeline stays current.

  • Planned
    Salesforce

    Contact and activity sync. On the roadmap, not built yet.

  • Planned
    Pipedrive

    Person and activity sync. On the roadmap, not built yet.

C · 3 integrations

Dialers

Hand the lead to a rep while the conversation is warm.

  • At launch · in validation
    Nooks

    Adds the lead to a Nooks list, right after a send or when they reply.

  • At launch · in validation
    Orum

    Adds the lead to an Orum queue, right after a send or when they reply.

  • At launch · in validation
    SalesFinity

    Adds the lead to a SalesFinity list, right after a send or when they reply.

D · 3 integrations

Automation

For everything without a native connection.

  • Launch
    Webhooks

    Posts reply, status and push events to any URL you choose.

  • Via webhooks
    Zapier · Make · n8n

    Catch imsgs webhooks to route replies into any tool your team runs.

  • Via API
    Clay

    Send enriched rows from a Clay table into a sequence through the API.

Using something that isn't listed? Tell us on a demo. Product names are trademarks of their owners and are shown only to describe compatibility.

02Dialer handoff

Two ways to hand a lead to the dialer.

Choose a mode per sequence, with a workspace default. Either way, a push adds the lead to a list or queue in Nooks, Orum or SalesFinity.

Workflow AWhen they answer

On reply

  1. Step 1 sends
  2. Lead replies
  3. Sequence stops
  4. Push

Only leads who answer reach the dialer, so reps call people who are already talking. Made for appointment setting.

Workflow BAfter Step 1

Immediate

  1. Step 1 delivered
  2. Push
  3. Sequence continues

Every delivered opener lands in the dialer queue, so reps can call while the text is fresh. Built for power-dialing a new list. A reply still stops the sequence, and you can stop it after a successful push too.

Sample data

Push status

Every push is tracked on the lead.

Each lead shows where it was sent and what happened, for the dialer and the CRM alike. Nothing fails silently.

  • Pending
    Pending

    Queued for the destination. Shown on the lead until it lands.

  • Pushed
    Pushed

    The dialer or CRM accepted it. Logged on the lead with a timestamp.

  • Failed
    Failed

    The destination rejected it. The reason is shown on the lead, with a one-click Retry.

  • Skipped
    Skipped (duplicate)

    Already pushed to that destination, so nothing is sent twice.

One push per lead, per destination.

If Dana is already in your Orum queue, a second push to Orum is skipped and logged instead of dialing her twice. HubSpot is a different destination, so her contact still syncs there.

03API & MCP

Build on it. Or let your agent.

A REST API for your own tools and an MCP server for AI agents, from your team or your clients. Clay, n8n and in-house scripts connect the same way. Docs ship with access.

Create a lead and enroll itIllustrative — API docs ship with access
POST /v1/leads
Host: api.imsgs.co
Authorization: Bearer $IMSGS_API_KEY

{
  "phone": "+15125550142",
  "first_name": "Dana",
  "company": "Whitfield Roofing",
  "workspace": "ridgeline-roofing",
  "enroll": { "sequence_id": "seq_q4_inspections" }
}

// 201 Created
{ "id": "lead_8f2k1", "imessage": "pending", "enrollment": "queued" }
  • Scoped keys per workspaceEach key belongs to one client workspace and only sees that workspace's data. 60 requests a minute by default.
  • Read everythingLeads, sequences, conversations, lines and push status, for reporting or your own agents.
  • Write what you allowCreate leads, enroll them, reply and push. Each action is its own scope.
  • Sending needs an explicit scopeA key can't start new outbound messages unless you grant it, so a reporting agent can never text a lead.

Docs

There are no public docs yet. API and MCP documentation ships with access, and we'll walk through your workflow on the demo.

Ask about API access

Bring your stack to the demo.

Tell us your CRM and dialer. We'll show the handoff end to end on a sample of your own leads.

Book a demo See pricing