Integration

SendGrid

Plandalf integrates with SendGrid as a email, website, sdk platform.

email website sdk

Visit SendGrid →

What it does

Sends emailEmail GIF promo Notifications
Custom HTML blocksTotally custom checkout layouts Buy button
Per-recipient timer imagesEmail GIF promo Deadline campaigns
Open APIAPI SDK

Product surfaces

Where SendGrid fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before SendGrid receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what SendGrid receives: product, price, buyer, checkout mode, invoice, and automation context.

Offers Products Prices Checkout templates

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before SendGrid enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

Checkout templates Order bumps Upsells Coupons

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

SendGrid should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Purchase automations Automations Sequences Webhooks

The Numi offer editor showing hosted checkout mode controls.

The buying surface can live where the buyer is

SendGrid can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.

Hosted checkout Buy button SDK checkout API-first stack

Overview

SendGrid is a transactional email platform. There’s no visual workflow builder for promo enrolment, so that path flows through Zapier or a direct Custom API call from the system that triggers each send — see those tabs for the setup.

What Plandalf does here

Countdown in dynamic templates — Handlebars-style {{email}} substitutes into the <img src> query string at render time, as long as the Mail Send API call includes email in dynamic_template_data.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire SendGrid into Plandalf.

promo · email

Drop the Plandalf countdown image into a SendGrid dynamic template

In your SendGrid Dynamic Template, paste this <img> tag into the HTML editor. SendGrid's templating uses Handlebars — {{email}} resolves to the recipient's address when the template data includes an email field (which is the convention for transactional sends).

<img
  src="{{ promo.countdown_url }}?ref={{email}}"
  alt="Time remaining on this offer"
/>

Make sure the dynamic_template_data payload you POST to the Mail Send API includes email alongside your other template vars, or swap in whichever field carries the address in your setup.

Automation graph

Connecting SendGrid

How SendGrid participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from SendGrid

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

sendgrid.subscriber_added: Fires when a new subscriber is added to SendGrid.
sendgrid.webhook: Fires when SendGrid POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on SendGrid

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

sendgrid.add_subscriber: Add a contact to a list or audience in SendGrid.
sendgrid.tag: Apply a tag or segment to an existing SendGrid contact.
sendgrid.send_email: Send a one-off transactional or broadcast email through SendGrid.
sendgrid.custom_api_call: Hit any SendGrid REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence

trigger: stripe.payment_succeeded
actions:
  - sendgrid.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Pair it with

Connect SendGrid with…

Platforms whose roles complement SendGrid inside a Plandalf sequence.

SendGrid + ActiveCampaign

Capture a lead on ActiveCampaign, nurture it through SendGrid.

SendGrid + beehiiv

Capture a lead on beehiiv, nurture it through SendGrid.

SendGrid + Kit (ConvertKit)

Capture a lead on Kit (ConvertKit), nurture it through SendGrid.

SendGrid + Customer.io

Capture a lead on Customer.io, nurture it through SendGrid.

SendGrid + Drip

Capture a lead on Drip, nurture it through SendGrid.

SendGrid + Flodesk

Capture a lead on Flodesk, nurture it through SendGrid.

See all integrations →

Integration methods

How SendGrid connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use SendGrid with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

Method 1
Embed a Plandalf buy button
Drop the Plandalf embed script into a SendGrid HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
```
<script src="https://cdn.plandalf.com/embed.js" async></script>

<button data-plandalf-present="offer_abc123">
  Buy now
</button>
```
Method 2
Drop in a per-recipient countdown image
Add an HTML block to any SendGrid email and paste the Plandalf countdown URL. SendGrid's merge tag `{{email}}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
```
<img
  src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{email}}"
  alt="Time remaining on this offer"
  width="600"
  height="120"
/>
```
Method 3
REST API webhook
For anything not covered by a native trigger, configure a SendGrid webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
```
curl -X POST https://api.plandalf.com/v1/webhooks/sendgrid \
  -H "Authorization: Bearer $PLANDALF_API_KEY" \
  -H "Content-Type: application/json" \
  -d @event.json
```

Official SendGrid docs and sign-up: sendgrid.com

FAQ

Common questions about the SendGrid integration

Do I need a paid plan to use SendGrid with Plandalf?

Plandalf itself is free to connect to SendGrid. You only need a SendGrid account that allows API access, which is almost every paid plan.

How long does setup take?

Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.

Can I disconnect SendGrid later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and SendGrid's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store SendGrid data?

Plandalf stores the SendGrid contact ID and the events Plandalf fired against that contact. Email content stays in SendGrid; Plandalf doesn't mirror your audience or newsletter archive.

What if my email need isn't covered by the actions or triggers listed here?

Use the generic `sendgrid.custom_api_call` action or the inbound `sendgrid.webhook` trigger. Anything SendGrid's REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

Plandalf respects SendGrid's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find SendGrid's own documentation?

SendGrid's homepage at https://sendgrid.com links to their developer docs. For Plandalf-side questions about the SendGrid integration, see the Plandalf docs.