Send SendGrid email from Notifly workflows, on your own account.

These are the fields the dashboard asks for when you connect SendGrid, quoted from the create form itself.

• Region. EU switches the SendGrid client to EU data residency before every send; Global (US) leaves it on SendGrid's default.
• IP Pool Name. Applied to every email from this integration when set. A trigger can override it for a single notification.
• From email address and Sender name. Sent as the From address and display name of every email this integration sends.

1. Sign in at app.notifly.io, open Integration Store in the sidebar and choose Connect Provider.
2. In the Connect Integration sheet, open the E-Mail tab (or search across channels), find SendGrid and choose Connect.
3. Pick the environment the integration belongs to. Development and Production keep separate integrations, so you can point each at a different SendGrid account or key.
4. Fill in Delivery Provider Credentials with the fields in the table above, then choose Create Integration.
5. A new integration starts switched on as both Active Integration and Primary Integration, so email steps in that environment send through SendGrid by default. If the environment already has a primary email integration, the dashboard asks before replacing it.

Your backend triggers a workflow; Notifly renders the email step and hands it to SendGrid. The subscriber is created or updated from to, so the first trigger for a new user needs no separate call.

// npm install @notiflyio/api@0.1.26
import { Notifly } from "@notiflyio/api";

const notifly = new Notifly({ security: { secretKey: process.env.NOTIFLY_SECRET_KEY } });

await notifly.trigger({
  workflowId: "password-reset",
  to: { subscriberId: "user_123", email: "ada@example.com" },
  payload: { resetUrl: "https://example.com/reset?token=abc" },
  overrides: {
    // Merged into this send's SendGrid request; it beats the integration's IP Pool Name.
    providers: { sendgrid: { ipPoolName: "transactional" } },
  },
});

Prefer plain HTTP? The same trigger is POST https://api.notifly.io/v1/events/trigger with an Authorization: ApiKey header and a body of { "name", "to", "payload" }.

• A category per workflow. The workflow identifier is set as the SendGrid category, so SendGrid's stats and event data split by workflow without extra work.
• Ids you can join on. Custom arguments carry Notifly's message, transaction, workflow and subscriber ids, and any customData a trigger passes.
• The full message. Cc and bcc recipients, reply-to, custom headers and attachments are carried onto the SendGrid message; attachments with a content id are sent inline.
• Your parameters, per trigger. Anything under overrides.providers.sendgrid is merged into the request for every SendGrid step of the workflow; overrides.steps.<stepId>.providers.sendgrid targets one step and wins over it.