Already have an account? Sign in

Mandrill

Mandrill feature snapshot

A high-level look at Stitch's Mandrill (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Mandrill

Connecting Mandrill to Stitch is a three-step process:

1. Add Mandrill as a Stitch data source
2. Define the Primary Key
3. Generate a Webhook URL
4. Set up webhooks in Mandrill

Add Mandrill as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theIncoming Webhooks icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Mandrill” would create a schema calledstitch_mandrill in the destination.Note: Schema names cannot be changed after you save the integration.

Define the Primary Key

Next, you’ll define the Primary Key for the data that your Mandrill integration will send to your data warehouse. A Primary Key is a field that’s used to uniquely identify each message in the webhook data.

Primary Keys must:

• Uniquely identify each message in the webhook data
• Have field names with 50 or less characters

• Be top-level fields. This means that Primary Key fields can’t be part of a nested object or array.

  If you need help determining if a field is part of a top-level record, we recommend looking for examples of the JSON record in your app’s API documentation. We’re always happy to help if you still aren’t sure.

Primary Keys and Replication Methods

Defining a Primary Key is optional, but theIncremental Replication Method Stitch uses to update your webhook integration’s data will depend on whether a Primary Key is provided or not.

• If a Primary Key is provided, replication to webhooks data will take place via an upsert. This means that existing rows can be updated.
• If a Primary Key is NOT provided:
  • Replication will beAppend-Only.
  • Stitch will auto-generate a field called__sdc_primary_key to be used as a Primary Key. This is because Stitch requires a Primary Key to replicate and de-dupe data.

Additionally, we don’t recommend changing a Primary Key once the integration has been set up and data has replicated. This could result in fields not being updated properly.

Enter the Primary Key into Stitch

In thePrimary Key field, enter the name of the field you want to use as a Primary Key. Note that this field isn’t required, but if left blank Stitch will auto-generate a Primary Key instead.

Generate a Mandrill Webhook URL

Once Stitch has successfully saved and created the Mandrill integration, you’ll be redirected to a page that displays your Mandrill webhook URL and token (which is blurred in the image below):

Click theCopy button to copy it.

Note that this particular URL won’t display in Stitch again once you click Continue. Think of this URL like you would your login or API credentials -keep it secret, keep it safe. You can, however,generate another URL should you need it.

Once you’ve copied your webhook URL, clickContinue to wrap things up in Stitch.

Set up webhooks in Mandrill

The last step is to setup webhooks in your Mandrill account.

1. Sign into your MailChimp account. (Yes, you read that right!)
2. Click theuser menu (your icon) > Account.
3. Click theTransactional tab.
4. ClickLaunch Mandrill.
5. Once you’re in the Mandrill app, click theSettings icon in the left nav tab.
6. Click theWebhooks tab.
7. ClickAdd a Webhook.

8. Check the events that you want to track. Every time one of these events occurs, the webhook will be triggered and data will post to your webhook URL:

   

9. In thePost to URL field, paste the Stitch-generated webhook URL.
10. Enter a briefDescription.
11. When you’re finished, clickCreate Webhook.

Replication

After you’ve successfully connected your Mandrill integration, Stitch will continuously replicate your webhook data into your destination.

• Webhooks and historical data
• How data is loaded into your destination
• How to query for the latest data

Webhooks and historical data

Because Mandrill data is sent to Stitch in real-time, this means thatonly new records are replicated to your destination. Most webhook-based integrations don’t retain historical data due to this as-it-happens approach.

In the event that our webhook service experiences downtime, you may notice some lag between an event occurring and the data appearing in your destination.

Loading behavior

This version of Stitch’s Mandrill integration loads data in an Append-Only fashion. When data is loaded using the Append-Only behavior, records are appended to the end of the table as new rows. Existing rows in the table aren’t updated even if the source has defined Primary Keys. Multiple versions of a row can exist in a table, creating a log of how a record has changed over time. Data stored this way can provide insights and historical details about how those rows have changed over time.

Refer to theUnderstanding loading behavior guide for more info and examples.

Query for the latest data

If you simply want the latest version of the object - or objects, if you elected to track more than one during the setup - in the integration’s table (data), you’ll have to adjust your querying strategy to account for the append-only method of replication. This is a little different than querying records that are updated usingupdated_at Incremental Replication.

To do this, you can use the_sdc_sequence column and the table’s Primary Key. The_sdc_sequence is a Unix epoch (down to the millisecond) attached to the record during replication and can help determine the order of all the versions of a row.

Note: If you didn’t define a Primary Key while setting up the integration, the Primary Key for the table will be__sdc_primary_key.

If you wanted to create a snapshot of the latest version of this table, you could run a query like this:

SELECT*FROM[stitch-redshift:stitch-mandrill.data]oINNERJOIN(SELECTMAX(_sdc_sequence)ASseq,[primary-key]FROM[stitch-redshift:stitch-mandrill.data]GROUPBY[primary-key])ooONo.[primary-key]=oo.[primary-key]ANDo._sdc_sequence=oo.seq

This approach uses a subquery to get a single list of every row’s Primary Key and maximum sequence number. It then joins the original table to both the Primary Key and maximum sequence, which makes all other column values available for querying.

Schema

In v1 of the Stitch Incoming Webhooks integration, Stitch will create a single table - calleddata - in the webhook integration schema (this will be the name you enter in theIntegration Schema field when you set up Mandrill) of your data warehouse.

The schema of this table will contain two “types” of columns:

• Columns used by Stitch (prepended with_sdc), and
• Columns sent by the provider’s webhook API

Aside from the Stitch columns, the schema of this table will depend entirely on Mandrill’s webhook API. With the exception of the_sdc fields, Stitch does not augment Incoming Webhooks data nor does it have any control over the fields sent by the webhook provider.

Webhook URLs & Security

Stitch allows you to generate up to 2 Mandrill webhook URLs at a time. These URLs contain security access tokens and as such, have access to your Mandrill account.

If you ever need to change your webhook URL, you can do so in the Integration Settings page after the integration has been created:

1. Click into the integration from the Stitch Dashboard page.
2. Click theSettings button.
3. In theWebhook URLs section, click theGenerate Webhook URL button.
4. A new webhook URL will display. Press theclipboard icon to copy it.
5. Follow the steps in theSetting Up Webhooks in Mandrill section to update the webhook URL in Mandrill.
6. After you’ve updated the webhook URL in Mandrill, click theRevoke button next to theoldest webhook URL in Stitch. This will invalidate the token and revoke access.

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.