Add recipients to intended list.
Input Fields
- List
- List ID* (number): Identification number of the list.
- Recipients
- Recipient IDs* (number): Identification number associated with recipient(s).
Output Fields
- There are no output fields
Start FLO when an email bounces.
Start FLO when an email is deferred.
Start FLO when a build finishes
Start FLO when an email is dropped.
Start FLO when a recipient opens an email.
Start FLO when an email is processed.
Start FLO when an email is marked as spam by a recipient.
Start FLO when a recipient clicks on a link in an email.
Start FLO when a recipient resubscribes to a specific group by updating their preferences.
Start FLO when a recipient clicks the “Opt Out of All Emails” link.
Start FLO when a recipient unsubscribes from a specific group, either by direct link or by updating their preferences.
Add recipients to intended list.
Output Fields
Add intended recipients to suppression group.
Output Fields
Create new campaign.
Output Fields
Create list within SendGrid.
Output Fields
Create new recipient in SendGrid.
Output Fields
This action allows you to make a custom, authenticated HTTP call to the Sendgrid REST API.
NOTE: Most of the operation can be found on documentation, we are using Web api v3!
Request Type (dropdown): your available HTTP request methods. There are 5 supported HTTP request methods (sometimes called verbs) in custom API calls:
GET: retrieves data from a web server based on your parameters. GET requests a representation of the specified resource, and if successful will receive a 2** OK response message with the requested content. Additional documentation here.
POST: sends data to a web server based on your parameters. POST requests include actions like uploading a file. Multiple POST’s may result in a different outcome than a single POST, so you should be cautious about unintentionally sending multiple POST’s. If a POST is successful, you will receive a 2** OK response message. Additional documentation here.
PUT: sends data to a location in the web server based on your parameters. PUT requests include actions like uploading a file. The difference between a PUT and POST is that PUT is idempotent, meaning that the result of a single successful PUT is the same as many identical PUT’s. If a PUT is successful, you will receive a 2** response message (usually 201 or 204). Additional documentation here.
PATCH: applies partial modifications to a resource on a web server based on your parameters. PATCH is not idempotent, meaning that the result of multiple PATCH’s could have unintended consequences. If a PUT is successful, you will receive a 2** response message (usually 204). Additional documentation here.
DELETE: deletes the specified resource from the web server based on your parameters (if the resource exists). If a DELETE is successful, you will receive a 2** OK response message (Usually 202). Additional documentation here.
Relative URL (text): the address on the web server you are attempting to interact with. Relative URL
means that you don’t have to explicitly specify the protocol at the beginning of the URL (such as “http://“). This suggests to the web server that the interaction is occurring on the server (in this instance). The {xx} need to be replaced by the respective argument.
Example: /now/{tablename}
Query (object or text): JSON object that determines the action taken at the URL.
Example: {"name":"something-urgent"}
Headers (object): JSON that determines the content type of the request. This will usually be a replica of the example below.
Example: {"Content-type":"application/json"}
Status Code (Number): the success or failure of your HTTP request. Here is a list of all status codes.
Headers (object): a more detailed context for the response/status code that doesn’t relate to the output body. Not all headers that appear in a response header are response headers, meaning that some are unlikely to be useful to you.
The response headers are dependent on the HTTP request you choose in options.
Deletes searched campaign.
Output Fields
Reads entire list of campaigns on SendGrid.
Output Fields
Click here for more information.
Read all lists on SendGrid.
Output Fields
Reads searched campaign.
Output Fields
Read list within SendGrid.
Output Fields
Read recipient in SendGrid.
Output Fields
Reads entire list of recipients on SendGrid.
Output Fields
Delete recipient from intended list.
Output Fields
Remove intended recipients from suppression group.
Output Fields
Schedule the time that the campaign will send.
Output Fields
Search Recipient in SendGrid.
Output Fields
Immediately send a marketing campaign.
Output Fields
Send Email.
Send a trigger email.
Output Fields
Click here for more information
Unschedule already scheduled campaign.
Output Fields
Update a campaign.
<title>, etc...
)Output Fields
Update recipient in SendGrid.
Output Fields
Update the time that a scheduled campaign will send.