Skip to main content
At Quixa, we believe in drinking our own champagne. Instead of relying on expensive external marketing automation SaaS platforms with rigid schemas and vendor lock-in, The Quixa Dispatch is powered entirely by Quixa’s visual workflow engine, scheduled triggers, and REST endpoints.

1. Architecture Overview

The automated newsletter pipeline operates on a decoupled architecture comprising a dedicated subscriber repository, secured management endpoints, and a visual workflow executed on a recurring cron schedule.

2. API Endpoints

The newsletter subsystem provides five core endpoints under /api/newsletter:

Subscribing a User

Fetching Active Subscribers


3. The Visual Workflow Recipe

You can build this automated campaign directly on the Quixa Canvas using the following drag-and-drop recipe:

Step 1: Fetch Active Subscribers Node

  • Node Type: http
  • Method: GET
  • URL: https://api.example.com/api/newsletter/subscribers?status=Active
  • Headers: X-Newsletter-Secret: {{variables.NEWSLETTER_SECRET}}

Step 2: For-Loop Iterator Node

  • Node Type: for
  • Collection: {{GetSubscribers.response.subscribers}}
  • Item Variable: subscriber
  • Index Variable: loopIndex

Step 3: Dispatch Issue Node

  • Node Type: http
  • Method: POST
  • URL: https://api.example.com/api/newsletter/send
  • Headers:
    • Content-Type: application/json
    • X-Newsletter-Secret: {{variables.NEWSLETTER_SECRET}}
  • Payload:

Step 4: Rate-Limit Throttle

  • Node Type: wait
  • Duration: 250ms (fixed buffer to stay within SMTP or provider limits).

Step 5: Terminal Completion Node

  • Node Type: stop
  • Scope: terminate-flow
  • Exit Status: Completed
  • Message: Newsletter campaign execution completed successfully.

4. Unsubscription & GDPR Compliance

Every email dispatched includes an RFC-compliant one-click unsubscribe URL containing an unguessable 128-bit cryptographic GUID token:
When clicked:
  1. The subscriber’s status is atomically changed from Active to Unsubscribed.
  2. The UnsubscribedAt timestamp is recorded.
  3. Subsequent workflow dispatch requests for this email address are immediately rejected with HTTP 400 Bad Request.
  4. The user is presented with a branded, dark-mode confirmation page with options to return to the homepage or resubscribe.