GoodSender icon

GoodSender

Send transactional, custom, and consent emails through GoodSender

Actions6

Email → Request Consent

AI-generated

Summary

Sends a POST to GoodSender's /v1/emails/consent endpoint, asking one recipient to approve future custom emails from your verified sender domain (the Permission Loop).

Inputs

  • domain (required) — Your verified sender domain the consent request is for.
  • email (required) — Recipient email address to request consent from.
  • recipientName — Optional display name stored for the recipient. It is trimmed. If non-empty, the recipient is sent as {email, name}. Otherwise only the address is sent.
  • redirectUrl — URL the recipient is sent to after responding. "{email}" is replaced with their address. Sent as redirect_url only when non-empty.
  • requestOptions — Node-level HTTP settings: batching (items per batch, default 50, and interval in ms, default 1000), ignore SSL issues, proxy, and timeout (default 10000 ms).

Output shape

The parsed JSON response from the GoodSender consent endpoint, returned as the node's output item(s). The source does not define its fields.

The request body contains domain, a one-element emails array, and optionally redirect_url. One request is made per input item. Authentication uses the goodSenderApi credential, and the base URL comes from the credential. The source does not show the response fields. Use Get Consent Status or List Consents afterwards to check whether the recipient has granted consent.

Examples

Example 1: Ask a new newsletter signup to opt in to custom emails from your domain.

domain=your-domain.com, email={{$json.email}}, recipientName={{$json.name}}, redirectUrl=https://your-domain.com/consent/{email}

Example 2: Request consent with no custom landing page.

domain=your-domain.com, email=user@example.com; leave Recipient Name and Redirect URL empty.

Links

Discussion