Overview
Connect SendGrid with Flows360
Email delivery service for sending transactional and marketing emails
Use the SendGrid connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and no declared triggers.
Available actions
- Send Email
- Send Dynamic Template
- Create or Update Contact
- Find List by Name
- Add to Global Unsubscribe List
- Remove from Global Unsubscribe List
- Check Global Unsubscribe Status
- Custom API Call
Available triggers
- No triggers are declared in this pinned package.
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: SendGrid
- Package:
@activepieces/piece-sendgrid@0.6.0 - Exact artifact digest:
sha256:4af83fc7b40b1a57c26c60b9b8eb73c6ae0acaa3be035e33088b6a0bfacfe9e5 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
SECRET TEXT, CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Send Email (
send_email), Send a text or HTML email Classification: read. - Send Dynamic Template (
send_dynamic_template), Send an email using a dynamic template Classification: read. - Create or Update Contact (
create_or_update_contact), Add or update a contact, optionally adding them to a list Classification: read. - Find List by Name (
find_list_by_name), Search for a list by its name Classification: read. - Add to Global Unsubscribe List (
add_to_global_suppression), Add one or more email addresses to the global suppression list, stopping all future emails to them Classification: read. - Remove from Global Unsubscribe List (
remove_from_global_suppression), Remove an email address from the global suppression list, allowing it to receive emails again Classification: read. - Check Global Unsubscribe Status (
check_global_suppression), Check whether an email address is on the global suppression list Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API Key Required · protected credential
connection_2 · custom
- API Key Required · protected credential
- Data Residency Required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Send Email | Yes | No | Send a text or HTML email |
| Send Dynamic Template | Yes | No | Send an email using a dynamic template |
| Create or Update Contact | Yes | No | Add or update a contact, optionally adding them to a list |
| Find List by Name | Yes | No | Search for a list by its name |
| Add to Global Unsubscribe List | Yes | No | Add one or more email addresses to the global suppression list, stopping all future emails to them |
| Remove from Global Unsubscribe List | Yes | No | Remove an email address from the global suppression list, allowing it to receive emails again |
| Check Global Unsubscribe Status | Yes | No | Check whether an email address is on the global suppression list |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Send Email · Read
Send a text or HTML email
send_email · Risk: low · Retry: safe
Inputs
to· array · Required, Emails of the recipientsfrom· string · Required, Sender email, must be on your SendGridfrom_name· string · Optional, Sender namereply_to· string · Optional, Email to receive replies on (defaults to sender)subject· string · Requiredcontent_type· string · Requiredcontent· string · Required, HTML is only allowed if you selected HTML as typeattachments· array · Optional
Send Dynamic Template · Read
Send an email using a dynamic template
send_dynamic_template · Risk: low · Retry: safe
Inputs
to· array · Required, Emails of the recipientsfrom_name· string · Optional, Sender namefrom· string · Required, Sender email, must be on your SendGridtemplate_id· string · Required, Dynamic template idtemplate_data· object · Required, Dynamic template datareply_to· string · Optional, Email to receive replies on (defaults to sender)attachments· array · Optional
Create or Update Contact · Read
Add or update a contact, optionally adding them to a list
create_or_update_contact · Risk: low · Retry: safe
Inputs
email· string · Required, Email address of the contact (used to match existing contacts)first_name· string · Optionallast_name· string · Optionallist_ids· array · Optional, Lists to add the contact tocustom_fields· object · Optional, Extra reserved (e.g. city, country) or custom fields as key/value pairs
Find List by Name · Read
Search for a list by its name
find_list_by_name · Risk: low · Retry: safe
Inputs
name· string · Required, The exact name of the list to search for
Add to Global Unsubscribe List · Read
Add one or more email addresses to the global suppression list, stopping all future emails to them
add_to_global_suppression · Risk: low · Retry: safe
Inputs
emails· array · Required, Email addresses to add to the global suppression list
Remove from Global Unsubscribe List · Read
Remove an email address from the global suppression list, allowing it to receive emails again
remove_from_global_suppression · Risk: low · Retry: safe
Inputs
email· string · Required, Email address to remove from the global suppression list
Check Global Unsubscribe Status · Read
Check whether an email address is on the global suppression list
check_global_suppression · Risk: low · Retry: safe
Inputs
email· string · Required, Email address to check
Custom API Call · Read
Make a custom API call to a specific endpoint
custom_api_call · Risk: low · Retry: safe
Inputs
url· object · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_is_binary· boolean · Optional, Enable for files like PDFs, images, etc.failsafe· boolean · Optional, On a failed request, output the error instead of failing the step.timeout· number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).followRedirects· boolean · Optional, Follow 3xx redirects instead of returning them as the response.
Setup
Setup
- Add the SendGrid connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- API Key (
apiKey), required; stored as a sensitive connection value. - Data Residency (
dataResidency), required.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-sendgrid@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 8 actions and 0 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Runtime execution evidence is managed separately from package metadata.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required SendGrid connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-sendgrid@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.