Docs / Data sources / Merge

Merge

Business software

Built when you ask for it

Sync Merge linked account, employee, candidate, and ticket data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Merge connector syncs your unified HR, ATS, CRM, and ticketing integration data into analytics-ready tables in your data warehouse. Pull linked accounts, employees, candidates, and tickets from the Merge API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Linked accounts
  • Employees
  • Candidates
  • Tickets

How it gets built

  1. Choose Merge when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Merge's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Merge itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Bearer token (API key) + X-Account-Token header. Get your org's API key from the Merge Dashboard; each end customer's Account Token is issued only after they connect via Merge Link.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Merge connector?
Not as a finished connector yet. Ingest builds it from Merge's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Merge data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Merge API documentation: https://docs.merge.dev/home

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Merge