OneLi with Make / Zapier
How to let an agent built with Make / Zapier place Hebrew phone calls through OneLi, follow the call, answer consultations and read the result.
In Make and Zapier, the tested path is an HTTP request to the REST API with the key in a header. Both also have an MCP Client app in beta, which we have not tested yet.
Setup
- Create an API key at oneli.io/app/connect and store it on the server as
ONELI_API_KEY.
Checked against: Make: HTTP module · Zapier: Webhooks by Zapier
Make: HTTP “Make a request”
URL: https://api.oneli.io/v1/call-tasks
Method: POST
Authentication: No authentication
Headers: Authorization: Bearer oli_…
Body content type: application/JSON
Body input method: JSON string
Body: {"idempotency_key":"…","to_number":"+972…","goal":"…"}
Parse response: YesZapier: Webhooks by Zapier → Custom Request
Method: POST
URL: https://api.oneli.io/v1/call-tasks
Data: {"idempotency_key":"…","to_number":"+972…","goal":"…"} (raw JSON, keep it non-empty)
Headers: Authorization: Bearer oli_…
Content-Type: application/jsonNotes
- Make MCP Client app (open beta): it has an “API Key / Access token” field or OAuth. We have not verified whether the field is sent as Bearer, or whether Make’s OAuth redirect URI is accepted by OneLi.
- Zapier MCP Client app (beta): Server URL, Transport Streamable HTTP, “Uses OAuth?” = No, oli_… as the bearer token. Not tested against OneLi.
- In Zapier keep Data non-empty, or Zapier sends every field from the previous step. Webhooks by Zapier is on paid plans only.
- Read the result later with GET /v1/call-tasks/:id.
Phone numbers: OneLi accepts an Israeli number in any common format (050-1234567, +972501234567). Once the call starts, the agent follows it with get_call_events or GET /v1/call-tasks/:id/events to answer consultations and get the summary.
Next steps
Sources: apps.make.com/http · apps.make.com/mcp-client · help.zapier.com/hc/en-us/articles/8496326446989 · help.zapier.com/hc/en-us/articles/38777069364109