Fax with Make (Integromat) — Using Our REST API
Send FAX Mail does not publish a dedicated Make app in the Make app directory. What works is Make's generic HTTP module calling our REST API, plus a Make webhook receiving our signed events. In a scenario you add an HTTP > Make a request module, point it at /v1/faxes, and pass your bearer key and the recipient — a fax goes out from any trigger you can build in Make. To react to results, a Custom webhook module gives you a URL you register at /dashboard/developers so our delivered, failed, and received events flow back into the same scenario. No hosting and no custom connector are involved.
Plan requirement
This uses our REST API and outbound webhooks, part of the Business ($79.99/mo) and Enterprise ($169.99/mo) plans. There is no Make-specific add-on from us and no listed connector; you build the flow with Make's own HTTP and webhook modules against our API.
How it works
Make's HTTP > Make a request module is a general-purpose caller: you set the method to POST, the URL to /v1/faxes, add an Authorization header carrying your bearer key, and give it a JSON body with a `to` number and either inline base64 or a public document_url. That single module turns any preceding module's output into a fax. For the reverse direction, the Custom webhook trigger mints a unique URL; you register it as a webhook endpoint at /dashboard/developers and subscribe it to the events you care about, and from then on our HMAC-signed posts start the scenario. Both directions are plain signed HTTP, so nothing is hosted outside Make and no code module is strictly required.
What you can do
- ✓Send a fax from any Make trigger with an HTTP > Make a request module aimed at /v1/faxes
- ✓Pass a public document_url so Make need not encode the file itself
- ✓Receive fax.delivered / fax.failed / fax.received on a Make Custom webhook
- ✓Route a delivered event onward to Google Sheets, Slack, or a CRM in the same scenario
- ✓Add an Idempotency-Key header so a scenario retry never sends the fax twice
- ✓Keep the flow connector-free using Make's standard HTTP and webhook modules
Setup steps
- 1Confirm the account is on Business or Enterprise so the API and webhooks are live
- 2Create an API key at /dashboard/developers with faxes:send (add faxes:read to poll)
- 3In Make, add an HTTP > Make a request module set to POST /v1/faxes
- 4Add an Authorization: Bearer header and a JSON body with `to` and `document_url`
- 5For inbound automation, add a Custom webhook trigger and copy its URL
- 6Register that webhook URL at /dashboard/developers and choose which events to forward
Example
# Make: HTTP > Make a request
Method: POST
URL: https://www.sendfaxmail.com/v1/faxes
Headers: Authorization: Bearer sfm_live_xxxxxxxx
Idempotency-Key: {{executionId}}
Body (JSON):
{ "to": "{{1.fax_number}}", "document_url": "{{1.file_url}}" }Make (Integromat) — FAQ
No. There is no listed app from us in Make's directory. You connect by pointing Make's generic HTTP > Make a request module at our /v1/faxes endpoint and by catching our events with a Make Custom webhook. These are standard Make modules, so the integration is real even though it is not a named connector.
Add an HTTP > Make a request module, set it to POST with the URL /v1/faxes, include an Authorization header with your bearer key, and build a JSON body carrying a `to` number and a document_url pointing at the file. When the scenario runs, that module calls our API and dispatches the fax.
Use Make's Custom webhook trigger. It generates a unique URL; register that URL as a webhook endpoint at /dashboard/developers and subscribe it to fax.delivered, fax.failed, or fax.received. Our signed event then starts the scenario, and you can branch on the status field to log, alert, or update a record.
It is worth doing for anything sensitive. Each event carries an X-SFM-Signature header; a small Make custom-function or code step can recompute the HMAC-SHA256 over the signed string using your endpoint secret and halt the scenario on a mismatch. If you skip that, keep the webhook URL private and accept that its secrecy is the only guard.
Build with the Make (Integromat)
API access and webhooks are included on the Business and Enterprise plans. Create a key at /dashboard/developers and start sending.
7-day free trial · No credit card required