SendGrid is an email delivery and marketing tool that lets you build and deliver personalized experiences through their API and marketing automation flows.

This document guides you in setting up SendGrid as a source in RudderStack. Once configured, RudderStack automatically ingests your SendGrid data and routes it to your specified data warehouse destination.

This source will be deprecated soon. Refer to the SendGrid V2 guide for the latest documentation.
All the Cloud Extract sources support sending data only to a data warehouse destination.

Getting started

To set up SendGrid as a source in RudderStack, follow these steps:

  1. Log into your RudderStack dashboard.
  2. Go to Sources > New source > Cloud Extract and select SendGrid from the list of sources.
  3. Assign a name to your source and click on Next.

Connection settings

  1. Click on Create Credentials from Scratch. You will then see the following screen:
SendGrid credentials
  1. Enter the following connection credentials to authenticate your SendGrid account with RudderStack:
  • Account Name: Enter your SendGrid account name (the email you used to sign up for SendGrid).
  • API Key: Enter your SendGrid API key by going to your SendGrid dashboard and navigating to Settings > API Keys.

For more information on the required permissions for the API key, refer to the FAQ section below.

Destination settings

The following settings specify how RudderStack sends the data ingested from SendGrid to the connected warehouse destination:

  • Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your SendGrid data into it.
  • Schedule Settings: RudderStack gives you three options to ingest the data from SendGrid:
    • Basic: Runs the syncs at the specified time interval.
    • CRON: Runs the syncs based on the user-defined CRON expression.
    • Manual: You are required to run the syncs manually.
For more information on the schedule types, refer to the Common Settings guide.

Selecting the data to import

Choose the SendGrid data that you wish to ingest via RudderStack. You can either select all the data or choose specific SendGrid data attributes as per your requirement.

Selecting the data to import

SendGrid is now configured as a source. RudderStack will start ingesting data from SendGrid as per your specified schedule and frequency.

You can further connect this source to your data warehouse by clicking on Add Destination, as shown:

Adding a destination
Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.


How do I obtain the SendGrid API key?

To obtain the API key for configuring the SendGrid Cloud Extract source, follow these steps:

  1. Log into your SendGrid dashboard.
  2. Go to Settings > API keys.
  3. Click on the Create API key option, as shown:
SendGrid API key
  1. Enter the name of the API key under the API Key Name field. In API Key Permissions, select Restricted Access.
SendGrid API key permissions
  1. Set the permissions as shown below:
SendGrid required permissions
  1. Finally, click on Create & View. Use these credentials to configure the source.
SendGrid API details
Copy the API key and store it securely. SendGrid will not display the API key again once you click on Done.

How does RudderStack sync the SendGrid data?

Upon configuring the source, RudderStack first connects to your SendGrid instance and pulls all the historical data. Subsequently, RudderStack syncs the SendGrid data based on your specified sync schedule and frequency.

Is it possible to have multiple Cloud Extract sources writing to the same schema?

Yes, it is.

RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page