Use your own email or mailing service
Connected campaigns, recipient files and delivery evidence—what works today, and what developers can integrate.
Choose how this stage goes out
A service connection is optional. In Messages & delivery, choose the file route to prepare a recipient snapshot for an email service, a mail merge or a print and fulfilment partner. Within the email campaign view, choose Send manually or use another service. Relae does not send email or physical mail itself.
- 1Review the stage's channel, audience, contact details and ask amounts, then prepare its recipient snapshot.
- 2Download the recipient file. Keep its matching identifiers when importing it into your service or producing a mail merge. Use only the fields your delivery partner needs.
- 3Design and send in your own service, or arrange the physical mailing. Downloading a file does not mark anyone as contacted.
- 4After the actual send, record the sent date or collect a delivery report. Review its column mapping and any unmatched recipients before applying evidence. Later replies and gifts can be reviewed separately.
Connected services
Mailchimp, Dotdigital and Emma have account connection paths. Choose an account once for the appeal, then review the campaign linked to each email stage. Existing stage overrides and prepared versions stay separate. Keep designing and sending in the provider; recipient lists are handed over by file. WordFly currently uses a manually saved campaign link, without automatic preview or result synchronization.
Available results depend on the provider. Emma can return campaign totals, including reported opens and clicks; these totals do not identify which appeal recipients engaged. A disconnected or unavailable service can still use recipient-file exports and reviewed result imports.
For developers
Relae does not currently provide a public integration API, customer API keys or published OpenAPI reference. Its signed-in download routes are not a supported machine-to-machine API. Do not build an integration by copying browser session credentials.
The planned API should support delivery channels rather than a fixed list of email vendors: authorized recipient snapshots, stable matching identifiers and imported delivery or response evidence. Email services, physical-mail fulfilment and custom workflows should use the same appeal and stage model, with channel-specific capabilities. This contract is planned, not available to call today.