Use Suped on Zapier to connect domain onboarding and email authentication data to your other apps. Suped provides actions that run after a trigger from another app or a schedule.
Connect Suped to a Zap
- Open the Suped integration listing, sign in to Zapier, and create a Zap.
- Choose and test the trigger that should start your workflow, such as a new client record in your CRM or a scheduled time.
- Add an action, select Suped, and choose the action you want to run.
- Connect your Suped account. In the authorization window, sign in to Suped, review the access request, and select Allow access. The connection uses your Suped login; you do not need a REST API key.
- Choose the organization and complete the fields required by the action. You can map values, such as a domain or client name, from the trigger's data.
- Test the action, check its result, and publish the Zap when it is ready. Testing an action that adds a domain or creates a client performs that action in your Suped account.
Start with List Organizations if you want to verify which organizations the connection can access. For help with the Zap editor, see Zapier's workflow guide.
Available actions
- List Organizations: Find accessible organizations, including MSP clients.
- List Domains: Retrieve an organization's monitored and archived domains.
- List Email Authentication Issues: Retrieve open, resolved, and dismissed issues for an organization.
- Get DMARC Records: Retrieve records between a start and end date. The range includes both bounds and is based on each report's end date.
- Download DMARC Report: Retrieve original report XML using its organization and report ID.
- Add Domain: Add a domain for monitoring or restore an archived domain in the selected organization.
- Create MSP Client Organization: Create a named client under an MSP you administer.
Example: onboard a domain from your CRM
Start with a CRM trigger for a client ready for onboarding. Add Suped's Add Domain action, choose the client's existing Suped organization, and map the CRM's domain field to the action's domain field. After a successful run, the domain appears in that organization. Follow Suped's DNS setup instructions at the domain's DNS provider to start receiving DMARC reports.
For a new MSP client, use Create MSP Client Organization first and pass the returned organization ID to Add Domain in a later action. Each successful client creation creates a separate organization; ensure the trigger represents a new client rather than every update to an existing client.
Use Suped through Zapier MCP
Suped on Zapier MCP makes the same actions available to compatible AI assistants. Open that page, follow Zapier's setup to create an MCP connection, connect your Suped account, and select the Suped actions you want to expose. Then connect your assistant using the server URL provided by Zapier.
To connect an assistant directly to Suped instead, use the Suped MCP server. Zapier workflows and Zapier MCP are subject to your Zapier account's usage limits.
Permissions and troubleshooting
Actions follow the connected Suped user's organization permissions. Reading domain data and adding domains require user or administrator access. Creating MSP clients requires administrator access to the parent MSP. A billing-only role cannot read domains, issues, or reports, or add domains.
These actions do not edit DNS, resolve or dismiss issues, delete domains or clients, or change account permissions. Adding a domain does not immediately produce reports; it still needs DMARC reporting configured and reports to arrive.
If an organization is missing, check the Suped account used by the connection and its permissions. If authorization expires, reconnect the account in Zapier. Inspect failed runs in Zap history before retrying client creation, since a previous attempt may already have created the client.
