Add or Update Contact: SendGrid action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email email	string	Required	Email. e.g. "user@example.com"
First Name first_name	string	Optional	Contact's first (given) name.
Last Name last_name	string	Optional	Contact's last (family) name.

Sample request

{
  "email": "user@example.com",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe"
}

Returns

{
  "job_id": "abc-123-def"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Add or Update Contact.

What does the Add or Update Contact action do in SendGrid?

Adds or updates (upserts) a contact in SendGrid marketing with email, name, custom fields, and list memberships. Used to keep your audience in sync with your CRM or product DB.

What inputs does Add or Update Contact require?

Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if SendGrid returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add or Update Contact support batch operations?

Yes. Run Add or Update Contact inside a Loop node to process arrays. Tiny Command handles SendGrid's rate limits automatically so you don't have to throttle manually.

More actions