Make.com

The iCallAgent app on Make's Developer Hub lets a Make user connect their iCallAgent workspace via OAuth2 (no manual API key) and build scenarios that push contacts into a call campaign from any Make trigger.

Connecting

From a Make scenario, add an iCallAgent module and create a new connection. You'll be sent through iCallAgent's standard OAuth2 consent flow: log in, pick the workspace this scenario should act on, and approve.

Modules

Module	Type	What it does
Send Contact	Action	Upserts a contact and queues a call, via POST /contacts/. Resolve the target campaign by id or by name.
Create Campaign	Action	Creates a new campaign via POST /campaigns/, deliberately separate from Send Contact: a scenario shouldn't create a new campaign on every contact.
Watch Completed Calls	Instant trigger	Fires once per call that reaches a terminal state, via a dedicated webhook subscribed through POST /webhooks/subscribe. See the call.completed payload.
Make an API Call	Universal	Lets you hit any /api/public/v1/... endpoint not covered by a dedicated module, reusing the connection's auth automatically.

Campaign, agent, and phone-number pickers in the module UI are backed by search RPCs (GET /campaigns/, GET /agents/, GET /phone-numbers/), the same list endpoints documented under API Reference.

Example scenario

Google Forms (new response)
  → iCallAgent: Send Contact
       phone:    {{form.phone}}
       name:     {{form.name}}
       campaign: "Inbound Leads"

Building your own equivalent

Everything the Make app does is available directly over the public API. See API Reference and Outbound Campaigns if you'd rather call iCallAgent from your own automation platform or backend.