Supaglue + Trigger.dev

In many situations, you will not read directly from the raw data that Supaglue lands into a database, e.g. when you already have an application data model (contact and account tables in your production database).

Instead, you will want to transform and enrich that data into more convenient models for your application using a transformation pipeline. Depending on your reliability requirements, you may wish to implement queueing, retries, and handling other scenarios for fault tolerance. Instead of building that infrastructure from scratch, you can leverage existing workflow engines like Trigger.dev.

Go end-to-end

Go through the following tutorials to build an end-to-end integration using Supaglue and Trigger.dev:

1. Go through Supaglue's Quickstart (approximately 10 minutes)
2. Go through Trigger.dev's Quickstart
3. Refer to our Transformations Tutorials for implementing common patterns for converting raw third-party provider data into your tables

Examples

• Common schema example
• Association bridge table example
• Object and field mapping example