Order confirmation in the shop's house design
A seller who maintains one set of SendGrid templates reuses the same dynamic template for purchases made in Plandalf, so receipts look like every other message.
Native on one side, webhook on the other
Stripe + SendGrid integration
Stripe takes the payment, Plandalf runs the checkout, and Send Webhook asks SendGrid to send a dynamic template to the buyer.
No credit card required. No coding required.
Stripe
SendGridDoes Stripe integrate with SendGrid?
Plandalf has no SendGrid steps and does not sync Stripe customers into SendGrid. A Send Webhook step can post to SendGrid's Mail Send API with your API key and a dynamic template ID, so a paid Stripe checkout, a refund or a failed payment sends an email from your own SendGrid account.
What moves between Stripe and SendGrid
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → SendGrid | Webhook | A Send Webhook step posts to the Mail Send endpoint. The buyer's address goes in the first personalization, and dynamic_template_data carries the product, total and invoice number for the template. |
| Cart recovery | Plandalf → SendGrid | Webhook | A declined card starts the trigger with a retry_url. Passing it in the template data puts the payment link in a SendGrid email. |
| Invoice refunded | Stripe → SendGrid | Webhook | A refund that succeeds in Stripe starts Invoice Refunded. Its refund amounts, such as refund_amount_formatted, can fill a refund confirmation template. |
| Countdown image in a template | Plandalf → SendGrid | A Plandalf promo image tag works in a dynamic template when the send call includes an email field in the template data to use as the ref. |
Send a SendGrid dynamic template after a paid checkout
You need a published Plandalf checkout on Stripe, a SendGrid API key with mail send permission, a verified sender and a dynamic template.
Prepare the template
In SendGrid create a dynamic template and note its ID, which starts with
d-. Write Handlebars placeholders such as{{name}}and{{total}}where the order details go.Create the sequence
In Plandalf open Automation, then My Sequences. Choose Plandalf, Checkout Completed, pick the offer and choose a recent checkout as the sample on the Test tab.
Add Send Webhook
Set POST and the URL
https://api.sendgrid.com/v3/mail/send. Add anAuthorizationheader that holds Bearer and your SendGrid key. Use the EU host instead if your regional subuser requires it.Write the JSON body
Set
fromto your verified sender,template_idto yourd-ID andpersonalizationsto a list whose first item hastoset to the buyer's{{trigger.customer_email}}anddynamic_template_dataholdingname,totalandinvoicevalues from trigger variables.Test and read the answer
A step test sends a real email, so address it to yourself. SendGrid answers HTTP 202 when it accepts the message, which is acceptance, not proof of delivery.
Rehearse with a test card
Switch on Run on test purchases, buy through the test link with a Stripe test card, then check the Events view and your inbox before you switch the setting off.
What sellers do with Stripe and SendGrid
Subscription dunning with a pay link
A software seller sends a failed-payment email from SendGrid that carries the retry_url, instead of using Plandalf's own recovery email.
Refund notice for a high-value order
A refund sequence sends a confirmation with the refunded amount, and a second step posts to an internal address so the team sees it.
Limits and gotchas
- SendGrid's Mail Send API requires
personalizationsandfrom, and each personalization needs ato. Do not mixsubstitutionswithdynamic_template_data, which is ford-templates only. - A 202 from SendGrid means the request was accepted. What happens to the message afterwards is visible in SendGrid, not in the Plandalf run.
- Plandalf's Send Webhook waits 30 seconds, sends the payload as JSON and promises no retries. An error body from SendGrid appears in the step output in the Events view.
- Plandalf has no SendGrid trigger, so anything that should flow back from SendGrid has to come through your own code or Zapier calling a Plandalf catch URL.
- Put the SendGrid key in the step headers only. Rotate it if it has ever been pasted into a page or a shared message.
Stripe and SendGrid: common questions
- Does Stripe integrate with SendGrid?
- Plandalf has no SendGrid app, so a paid Stripe checkout reaches SendGrid through a Send Webhook step that calls its Mail Send API. For other Stripe routes, check SendGrid's own integrations list.
- How do I send Stripe purchase emails with SendGrid?
- Build a dynamic template in SendGrid, then add a Send Webhook step to a Plandalf sequence on Checkout Completed that posts to the Mail Send endpoint with your API key and template ID.
- Should I use SendGrid or Plandalf's Send Email?
- Use Plandalf's Send Email if a plain message from a verified domain is enough. Use SendGrid when you already have templates, suppression lists or a sending reputation there.
- Why does SendGrid return 202 but no email arrives?
- 202 means SendGrid accepted the request. Check the template ID and the verified sender, then look in SendGrid for what happened to the message after that.
Guides for this pair
- Plandalf with Stripe
- Plandalf with SendGrid
- Automations overview
- Webhooks and catch URLs
- Create a promo
More from Stripe and SendGrid
- Stripe + VueA Vue 3 component renders a button, the browser SDK opens the checkout, and your Stripe account takes the payment.
- Stripe + WebflowStyle the button in Webflow Designer, add one custom attribute, and a Plandalf checkout charging your Stripe account opens from it.
- Stripe + WordPressWordPress stays the page; a Plandalf button or inline checkout on it takes payment through your connected Stripe account.
- HubSpot + SendGridPlandalf does not sync HubSpot with SendGrid. It sits beside both: checkout events by webhook, countdown images in the emails each one sends.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Twilio SendGrid docs: Mail Send API.