Integrately and Groundmail
Send email from an Integrately automation with its Webhook/API app as the action, which makes an HTTP request to the Groundmail API.
Integrately's own documentation covers choosing the Webhook/API app and the HTTP method, but not every field on the action screen, so the table below names settings by what they do. Match them to the labels you see.
Prerequisites
- A Groundmail account with a verified sending domain.
- A Groundmail API key. Create one under API Keys in the dashboard. Choose Send only, and limit it to your sending domain with the allowed domains option. See API keys.
- An Integrately automation with a trigger that provides the recipient's email address.
1. Add the action
- In your automation, choose the trigger app, then search for Webhook/API and set it as the action app.
- Choose the POST method.
- Enter the request:
| Setting | Value |
|---|---|
| URL | https://api.groundmail.dev/emails |
| Header | Authorization: Bearer gm_… |
| Header | Content-Type: application/json |
| Body (JSON) | The message, below |
{
"from": "notifications@yourdomain.com",
"to": "user@example.com",
"subject": "Your order has shipped",
"html": "<p>Your order is on its way.</p>",
"text": "Your order is on its way."
}Replace to, subject and the body with values from your trigger. from must be on a verified domain, and at least one of html or text is required. See Emails for every field.
If the action screen has no field for headers or a JSON body, Integrately cannot make this request in that automation. Use Zapier, Make or Pabbly Connect instead.
2. Test it
Run the action with a test key (gm_test_…, created by ticking Test key on the API Keys page). Groundmail runs the whole pipeline but delivers nothing, so any recipient works. A successful response looks like this:
{ "id": "msg_…", "status": "sent", "test": true }You can also use a live key and send to delivered@simulator.groundmail.dev, which never reaches a real inbox. Use bounce@simulator.groundmail.dev to see a hard bounce. The full list is in Testing. The email shows up under Emails in the Groundmail dashboard. When you are done, replace the test key with a live key.
Troubleshooting
401 unauthorized. The header value must be Bearer gm_…, with the word Bearer and a space. Check the key is active on the API Keys page.
403 forbidden. The domain in from is not verified on your account, or the account is still on the sandbox sender, which only sends to your own account email. Verify the domain under Domains. A 403 domain_not_allowed means the key is limited to other domains, and insufficient_scope means the key cannot send.
400 validation_error. A required field is missing or empty, to is not a valid address, or the body is not valid JSON. The message and details in the response say which field. See Errors.
422 validation_error with suppressed. Every recipient is on your suppression list or was held back as unable to receive mail. Do not retry the same address; see Suppressions.
429. You hit a sending limit. See Sending limits.