GoodSender icon

GoodSender

Send transactional, custom, and consent emails through GoodSender

Actions6

Email → Get Consent Status

AI-generated

Summary

Look up the current consent status of a single recipient email address in GoodSender, optionally narrowed to one sender domain.

Inputs

  • email (required) — Recipient email address to look up. URL-encoded and placed in the request path (GET /v1/emails/{email}).
  • domain — Filter By Domain. Sent as the domain query parameter. Leave empty to return consent across all domains.
  • requestOptions — Node-level HTTP options: batching (items per batch, default 50; interval, default 1000 ms), ignore SSL certificate issues, proxy URL, and timeout (default 10000 ms).

Output shape

The JSON response from GoodSender's GET /v1/emails/{email} endpoint, returned as output item(s) for each input item. It holds the recipient's consent status.

The source doesn't define the response fields. They are whatever the GoodSender API returns. Requires GoodSender API credentials, and the request goes to the base URL set in those credentials. Errors such as an unknown recipient or a bad credential come from the API and follow n8n's standard HTTP error handling.

Examples

Example 1: Check whether a recipient has approved custom email before sending.

Email = {{$json.email}}; leave Filter By Domain empty.

Example 2: Check consent for one specific sender domain.

Email = user@example.com; Filter By Domain = your-domain.com.

Links

Discussion