Skip to main content
Use SendGrid Dynamic Templates to email your customers when their shipment is sent or the carrier reports a new tracking scan. The emails go out from your own SendGrid account and your own address. Zippendo does not email your customers itself; it tells SendGrid which event happened.
Product overview: SendGrid on zippendo.com

​
Before you start

  • A SendGrid API key that is allowed to send mail.
  • A sender address that is verified in SendGrid, and the name to show as the sender.
  • A Dynamic Template in SendGrid for each event you want to email about.
  • The Growth, Pro or Enterprise plan in Zippendo.

​
Events SendGrid can email about

  • Shipments: Shipment created, Shipment sent, Shipment cancelled
  • Tracking: Tracking updated
SendGrid has no order events.
Each event needs a Dynamic template ID, and the app has no field for it. It can only be set for each event through the Zippendo API, so ask your developer or contact support to set it. Without a template for an event, SendGrid has no email to send and refuses the delivery.

​
Connect SendGrid

1

Prepare the templates in SendGrid

Create a Dynamic Template for each event you plan to email about, for example “on its way” and “tracking update”.
2

Open the catalog

In Zippendo, click Apps & integrations in the sidebar, then Catalog, and click Connect on SendGrid under Apps. Read what Zippendo will do and click Continue.
3

Enter your details

Type a Connection name and fill in API key, From email and From name. From email must be a sender you verified in SendGrid.
4

Pick the events

Tick the events that should send an email, then click Connect.
5

Check it

Send a shipment for an order with a customer email, then look in the connection’s delivery log (the plug icon) and in SendGrid’s activity.
Every field and message is described in Connect SendGrid.

​
After connecting

  • Make sure each event you ticked has its template set.
  • Use Automations if only some shipments should get an email, such as shipments abroad.

​
Troubleshooting

  • 403 in the delivery log: the sender address is not verified in SendGrid, or the key is not allowed to send mail.
  • 400 in the delivery log: SendGrid could not build the email, for example because the event has no template, the template ID is mistyped, or the order has no customer email.
  • A failed test event: a test event has no customer and no template, so SendGrid refuses it. Check with a real shipment instead.
See also Integrations troubleshooting.