Send plain text email
Submit one plain text message; sandbox mode validates without sending.
Connector library
SendGrid connector.
Submit plain text email, upsert an email-identified marketing contact, inspect asynchronous contact import jobs and retrieve contacts through SendGrid v3.
Connector download
Download SendGrid
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Base URL
- Package size
- 10 KB
- SHA-256
ace97e5ce9838d2fdd7e0df8ccd750a5b174bb18cdd46e15f87cba9bbfc57f29
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-03 · Implemented source
Submit plain text email, upsert an email-identified marketing contact, inspect asynchronous contact import jobs and retrieve contacts through SendGrid v3.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Retained immutable historical scaffold archive.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
Upsert email contact
Queue one email-only contact profile update without hidden polling.
Get contact import job
Inspect one upsert/delete job; partial or complete failure returns an error.
Find contact by email
Retrieve a primary/alternate email match; found=false means no match.
Get contact
Retrieve a marketing contact by its vendor ID.
Vendor API
API and access
Implementation considerations
- Protocol connectors are intentionally broad; start with simple get/create/update/delete or send/receive operations and add schema-specific behavior per customer.
- Confirm authentication, TLS, VPN/private networking, payload schema, idempotency keys, rate limits, and retry expectations.
- Keep secrets out of payloads, prompts, and logs; store credentials centrally and redact sensitive fields.
Related connectors
More in APIs, Messaging & Protocols
Support
Need help with SendGrid?
Tell us what you need to connect or change.