Fax Automation with AI

Fax automation with Claude, ChatGPT or your own agent means the routine fax work, such as checking what arrived, watching delivery and chasing failures, happens from a prompt or a script instead of by hand in the dashboard. Fax.Plus offers three layers for this: an MCP connector for assistants, webhooks and a REST API for code, and no-code integrations. Here is what each one is for and how to start safely.

Before you start

• Use an active Fax.Plus Basic plan or higher and an existing authorized Fax.Plus MCP connection. New here? Start at the MCP setup hub.
• MCP is unavailable for accounts with Advanced Security Controls, including HIPAA and PHIPA configurations.
• Whether a prompt can run on a schedule depends on your AI client. Check the first runs by hand before you rely on them.

1. Morning digest

Have your assistant summarize what arrived overnight. This is read-only: it looks at your inbox and changes nothing. Related guide: Find and read a received fax.

2. Delivery watch

Ask for a status check on what you sent and what is still waiting. Also read-only. Related guide: Check fax delivery.

3. Failed-fax recovery

Find what failed and why, then decide. Looking is read-only; resending changes data, so the prompt asks for your OK first. Related guide: Resend a failed fax.

4. Run it from your own agent

For code and headless runs, connect your own agent to https://mcp.fax.plus/mcp with a personal access token (PAT). PATs are an Enterprise feature; on Basic, Premium and Business use an OAuth-capable client such as Claude or ChatGPT.

1. In Fax.Plus open Settings → Integrations, then Personal Access Tokens → Manage.
2. Create a token. Start read-only with fax:all:read and add fax:fax:edit or fax:all:edit only if the agent has to send or manage faxes.
3. Copy the token right away, since it is shown once, and store it as a secret.

Examples for the Anthropic API (MCP connector) and the OpenAI Agents SDK, as published in the official MCP documentation. Check each provider's current docs for model names and parameters.

5. Webhooks for events

MCP answers when your assistant asks. If you want Fax.Plus to tell your own system when something happens, such as a fax arriving or a delivery result, use webhooks. Webhooks are REST-only, not MCP tools. You can set them up in Settings → Integrations or through /v3/webhooks, and the endpoints are signed with HMAC-SHA256, so your server should verify the signature. The REST API is part of the Enterprise plan; see the Fax.Plus API page and the webhook guide in the API documentation.

6. No-code integrations

If you would rather not write code, the Fax.Plus integrations connect faxing to the tools you already use. They are a different path from MCP, so pick whichever fits the task.

Keep automation safe

• Recurring runs stay read-only. Digests and status checks are fine to repeat. Do not leave a recurring task that sends, resends or deletes faxes running without a person approving each action.
• Approval depends on your client. Keep the Fax.Plus tools that send or change data on the setting that asks first.
• If a run fails, check before retrying. Do not assume nothing was sent: look at the outbox and sent faxes first.
• Some work is REST only. Buying or releasing numbers, balance, team management, account settings, webhooks and bulk deletion are not MCP tools.

Examples by sector

See how the same routines look in a real workflow: law firms, real estate closings, insurance claims intake, permit filings, small business, purchasing, HR onboarding, legal aid and nonprofits, school administration, auto dealers and lending, telecom and utilities, and for individuals faxing a signed document.

Related

More copy-ready prompts are in Fax Prompts with AI. Not sure whether MCP or the API fits? Read MCP or REST API: which to use.