SendGrid · Email event — When an email SendGrid sent is delivered, opened, clicked, bounces or is marked spam — starts a run for each event SendGrid reports about your email. Use it to remove bounced addresses from a list, alert someone when a customer opens a quote, or record what happened to each email.

It is an instant trigger. SendGrid only sends events to an address set in its own dashboard, so you paste the trigger's address there once — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan — SendGrid is not a premium connection. The address appears once an Admin or Editor has opened the trigger; Viewers see it after that.

On SendGrid's side, someone who can change Mail Settings — usually the account's owner or an administrator.

Before you start

A SendGrid connection — see Connect SendGrid.

Steps

In Bizomate:

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under SendGrid, select Email event — it reads SendGrid · instant. Or type SendGrid in Search triggers.
  3. In Connection, choose your SendGrid connection — for example Consulace SendGrid.
  4. In Event, choose which events start a run:
    • Every event — the default. Every event SendGrid sends is a run.
    • Delivered, Opened, Clicked or Marked spam — only that one.
    • Bounced or dropped — bounces, and emails SendGrid dropped without sending.
  5. Under One step in SendGrid, select Copy beside Webhook address. A toast says Copied — The address is on your clipboard.

In SendGrid:

  1. Sign in at app.sendgrid.com and open Settings › Mail Settings › Event Webhook.
  2. Paste the address as the webhook's URL.
  3. Tick the events to send. SendGrid sends only these; Event in Bizomate then chooses among them.
  4. Optional, and recommended: enable Signed Event Webhook. SendGrid shows a verification key. Copy it.
  5. Save.

Back in Bizomate:

  1. If you enabled signing, paste the key in Verification key — Optional — SendGrid › Settings › Mail Settings › Event Webhook › Enable Signed Event Webhook: the key it shows. With it, Bizomate checks every event is SendGrid's.
  2. The panel reads Waiting for the first event — Send an email through SendGrid, or use Test Your Integration there; it appears here within seconds.
  3. Send an email with SendGrid · Send an email, or use Test Your Integration on SendGrid's Event Webhook page. The panel reads Listening — instant — Last event 10:45 · delivered · rohan@consulace.com.
  4. On Output, select Use the last event. Test run starts with that event.
  5. Add the steps, test, then Publish.

You can paste the address and test before publishing: events arrive and show on the panel, but start runs only once the workflow is published and switched on.

What the trigger gives

Each event is one item:

Field What it is
event What happened — delivered, open, click, bounce, dropped, spamreport, and others SendGrid sends with Every event.
email The recipient's address — rohan@consulace.com.
timestamp When it happened, in UTC — 2026-10-02T09:30:00Z.
messageId SendGrid's id for the email.
url The link that was clicked, for a click.
reason Why it bounced or was dropped.
category The email's categories in SendGrid, if it had any.

Use them in later steps as {{ trigger.email }}, {{ trigger.event }} and so on.

What happens next

  • Each event starts one run of the live version, in Production, named after it — bounce · rohan@consulace.com. SendGrid sends events in batches; every event in a batch is its own run.
  • The address stays the same across publishes, so SendGrid is set up once.
  • Changing to another trigger and publishing, or deleting the workflow, retires the address: SendGrid's calls to it are answered No workflow listens here. Remove it from SendGrid too.

Good to know

  • With a Verification key, every batch is checked. A batch whose signature does not match the key is answered 401 — The signature does not match. — and none of its events start a run or show on the panel. Without a key, the 48-character code in the address is the only check.
  • Opens are estimates. SendGrid counts an open when the email's images load; some mail apps load them for every email, others never do.
  • Event chooses among what SendGrid sends. An event not ticked in SendGrid never arrives, whatever Event says.
  • Each workflow has its own address. For a second workflow, add a second Event Webhook in SendGrid if your plan allows it.
  • Runs count in the month's allowance. Every event on a busy account means many runs — choose only the events you act on.

If something goes wrong

What you see Why What to do
Waiting for the first event stays after emails were sent The address was not saved in SendGrid, the event is not ticked there, or the Verification key does not match. Check the URL and ticked events in SendGrid. Copy the verification key again, or clear Verification key to test without it.
SendGrid's Test Your Integration reports 401 Verification key is filled in, but Signed Event Webhook is off, or the key is from another webhook. Enable signing in SendGrid and copy its key again.
No One step in SendGrid box and no address The trigger was opened by a Viewer before anyone who can edit. Ask an Admin or Editor to open the trigger once.
Nothing has arrived yet — make one happen in SendGrid, then try again. on Output No event has reached the trigger yet. Send an email, or use Test Your Integration.
Events show on the panel, but no run starts The workflow is not published, or is switched off. Publish it, and switch it on.
An event never shows on the panel Event leaves it out, so it is not taken at all. Choose Every event, or the event you want.