HTTP Request and SendGrid integration

Save yourself the work of writing custom integrations for HTTP Request and SendGrid and use n8n instead. Build adaptable and scalable Development, Core Nodes, Marketing, and Communication workflows that work with your technology stack. All within a building experience you will love.

Get started

See n8n in action

How to connect HTTP Request and SendGrid

Step 1: Create a new workflow
Step 2: Add and configure nodes
Step 3: Connect
Step 4: Customize and extend your integration
Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

HTTP Request and SendGrid integration: Create a new workflow and add the first step

Step 2: Add and configure HTTP Request and SendGrid nodes

You can find HTTP Request and SendGrid in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure HTTP Request and SendGrid nodes one by one: input data on the left, parameters in the middle, and output data on the right.

HTTP Request and SendGrid integration: Add and configure HTTP Request and SendGrid nodes

Step 3: Connect HTTP Request and SendGrid

A connection establishes a link between HTTP Request and SendGrid (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

HTTP Request and SendGrid integration: Connect HTTP Request and SendGrid

Step 4: Customize and extend your HTTP Request and SendGrid integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect HTTP Request and SendGrid with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

HTTP Request and SendGrid integration: Customize and extend your HTTP Request and SendGrid integration

Step 5: Test and activate your HTTP Request and SendGrid workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from HTTP Request to SendGrid or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

HTTP Request and SendGrid integration: Test and activate your HTTP Request and SendGrid workflow

Track investments using Baserow and n8n

This workflow uses a number of technologies to track the value of ETFs, stocks and other exchange-traded products:

Baserow: To keep track of our investments
n8n’s Cron node: To trigger the workflow compiling our daily morning briefing
Webscraping: The HTTP Request & HTML Extract nodes to fetch up-to-date prices from the relevant stock exchange and structure this infromation
Javascript: We’ll use the Function node to build a custom HTML body with all the relevant information
Sendgrid: The Email Service Provider in this workflow to send out our email

Thanks to n8n, the steps in this workflow can easily be changed. Not a Sendgrid user? Simply remove the Sendgrid node and add a Gmail node instead. The stock exchange has a REST API? Just throw away the HTML Extract node.

Here’s how it works:

Data Source

In this scenario, our data source is Baserow. In our table, we’ll track all information needed to identify each investment product:

We have two text type columns (Name and ISIN) as well as two number type columns (Count and Purchase Price).

Workflow

Nodes

1. Cron

The Cron node will trigger our workflow to run each work day in the morning hours.

2. Baserow

The Baserow node will fetch our investments from the database table shown above.

3. HTTP Request

Using the HTTP Request node we can fetch live data from the stock exchange of our choice based on the ISIN. This example uses Tradegate, which is used by many German fintechs. The basic approach should also work for other exchanges, as long as they provide the required data to the public.

4. HTML Extract

Since our HTTP Request node fetches full websites, we’re using the HTML Extract node to extract the information we’re looking for from each website. If an exchange other than Tradegate is used, the selectors used in this node will most likely need to be updated.

5. + 6. Set

The Set nodes helps with setting the exact columns we’ll use in our table. In this case we’re first formatting the results from our exchange, then calculate the changes based on the purchase price.

7. Function

Here were using a bit of Javascript magic to build an HTML email. This is where any changes to the email content would have to be made.

8. Sendgrid

Finally we send out the email built in the previous step. This is where you can configure sender and recipients.

Result

The basic email generated by this workflow will look like so:

Nodes used in this workflow

Get started

Copy workflow

Popular HTTP Request and SendGrid workflows

Track investments using Baserow and n8n

This workflow uses a number of technologies to track the value of ETFs, stocks and other exchange-traded products: Baserow: To keep track of our investments n8n’s Cron node: To trigger the workflow compiling our daily morning briefing Webscraping: The HTTP Request & HTML Extract nodes to fetch up-to-date prices from the relevant stock exchange and structure this infromation Javascript: We’ll use the Function node to build a custom HTML body with all the relevant information Sendgrid: The Email Service Provider in this workflow to send out our email Thanks to n8n, the steps in this workflow can easily be changed. Not a Sendgrid user? Simply remove the Sendgrid node and add a Gmail node instead. The stock exchange has a REST API? Just throw away the HTML Extract node. Here’s how it works: Data Source In this scenario, our data source is Baserow. In our table, we’ll track all information needed to identify each investment product: We have two text type columns (Name and ISIN) as well as two number type columns (Count and Purchase Price). Workflow Nodes 1. Cron The Cron node will trigger our workflow to run each work day in the morning hours. 2. Baserow The Baserow node will fetch our investments from the database table shown above. 3. HTTP Request Using the HTTP Request node we can fetch live data from the stock exchange of our choice based on the ISIN. This example uses Tradegate, which is used by many German fintechs. The basic approach should also work for other exchanges, as long as they provide the required data to the public. 4. HTML Extract Since our HTTP Request node fetches full websites, we’re using the HTML Extract node to extract the information we’re looking for from each website. If an exchange other than Tradegate is used, the selectors used in this node will most likely need to be updated. 5. + 6. Set The Set nodes helps with setting the exact columns we’ll use in our table. In this case we’re first formatting the results from our exchange, then calculate the changes based on the purchase price. 7. Function Here were using a bit of Javascript magic to build an HTML email. This is where any changes to the email content would have to be made. 8. Sendgrid Finally we send out the email built in the previous step. This is where you can configure sender and recipients. Result The basic email generated by this workflow will look like so:

Build your own HTTP Request and SendGrid integration

Create custom HTTP Request and SendGrid workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.