How does OCNORA authenticate with COAX Email API?

With a stored API key credential, shaped {"api_key"} or {"username", "password"}. A connection test can check it when you add it.

What can I automate with COAX Email API?

COAX Email API has no typed nodes of its own. Your COAX Email API connection is used by Send Email (mail.send).

What if the COAX Email API operation I need is not listed?

Where COAX Email API has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use COAX Email API?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are COAX Email API calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

COAX Email API

EmailAPI keyConnection test available

COAX customer email API over HTTPS. Supports configurable method, endpoint, headers and payload mapping for mail.send.

COAX Email API has no typed nodes of its own: it connects as a stored credential that the generic Send Email node uses — the node picks COAX Email API from the connection you select.

Ask about COAX Email API

Before you connect COAX Email API

Authentication: API key
Credential: {"api_key"} or {"username", "password"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with COAX Email API

Operations of the generic nodes your COAX Email API connection drives, grouped by what they do to your data.

Create and send 1

Send Email

Nodes that use your COAX Email API connection

These generic nodes accept your COAX Email API credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.

Send Email
mail.send
Send an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.
Also works withSendGrid SMTP Hostinger Email Outlook / Microsoft 365 Gmail

A sample COAX Email API workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no COAX Email API trigger is needed.
2
Send Emailmail.send
Send an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

COAX Email API questions

How does OCNORA authenticate with COAX Email API?: With a stored API key credential, shaped {"api_key"} or {"username", "password"}. A connection test can check it when you add it.
What can I automate with COAX Email API?: COAX Email API has no typed nodes of its own. Your COAX Email API connection is used by Send Email (mail.send).
What if the COAX Email API operation I need is not listed?: Where COAX Email API has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use COAX Email API?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are COAX Email API calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first COAX Email API workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales