How it works
Verify a domain in Organization → Integrations & Domains. Only verified exact ORIGINAL sender domains are accepted, including forwarded emails. An original gmx.de sender stays blocked if only prange.io is verified. Sender authentication, spam and malware checks still apply. The forwarding mailbox domain does not grant access.
The designer disables email triggers until domain configuration is ready. Inserting one saves the draft and reserves a unique address bound to organization, flow and node. Copy it from the node settings and publish the flow before sending email. No separate inbox integration, signing key or customer MX changes are required.
API: POST /v1/designer-flows or save a draft with start.trigger={kind:email,integrationId:null}. The returned draft contains its allocated integrationId; GET /v1/integrations returns the matching destination and verifiedSenderDomains. Ordinary saves retain the address. Removing or replacing the email start on a draft/version write revokes the old address and routing immediately; old addresses cannot be restored by undo or copied to a different flow. Re-inserting creates a fresh address. Running processes and historical versions remain immutable. UI removal requires confirmation.
Only the platform gateway calls /v1/inbound-email/{integrationId}/context|upload|confirm|receive with the server-only platform HMAC secret. Full subject/message are stored as private source context, never copied into generic run.data. A default optional emailAttachments document field is created; set documents[].required=true for mandatory attachments. Attachments use private scanned S3 document uploads with the existing approver-only access. The central platform receiving domain retains its shared SES/MX infrastructure; nothing is provisioned per customer or trigger.
Request essentials
- Authorization
- Bearer $FLOW2ACT_API_KEY
- X-Organization-Id
- Your workspace UUID