Data pipelines (out)

Data pipelines move your collected data out of e-satisfaction and into your own data storages and downstream tools. Whether you want to run large analytical queries in a warehouse or push each survey completion to your own systems in real time, this is where you wire those connections up. You manage them in Admin → Integrations.

Data Warehouse Access

Data Warehouse Access is a managed BigQuery dataset you can connect to directly with a service account key. All of the data you collect flows into it, so it's the place to run analytics and large queries against your full dataset — from your own BI tools, notebooks or SQL clients.

To understand what's inside and how to keep your own database in sync, see the full Data Warehouse guide. The public schema documentation lists every available table and column: Schema documentation.

Getting access

Access is request-based for now

Self-serve access Coming soon is under development. For now, open a support ticket and we will take care of it — the team enables access for your organization and sends you the service-account credentials to connect with.

Open a support ticket

Request Data Warehouse Access through the support portal: Open a support ticket.

We enable it for you

The team provisions your warehouse access and sends over your service-account credentials. See Sharing access between projects for exactly what's exchanged.

Connect and query

Use the service account key to connect from your BI tool or SQL client, and query your data using the schema documentation as your map.

Webhooks

Webhooks push events to your own endpoint the moment they happen, so your systems stay in sync without polling. A webhook fires on the "Questionnaire Completed" event — one delivery per completion — sending an HTTP POST to the endpoint you specify.

Each delivery carries the completion data, including:

Instance and organization IDs
Survey details and the responder
The answers submitted
Metadata, segments and campaigns
Timestamps

One webhook can cover many surveys, across any of your workspaces. Every survey you choose sends its completions to the same endpoint, with the same settings — and you manage it as a single webhook.

Add a webhook

Allow our webhook IP address

Before anything will arrive, add e-satisfaction's webhook IP address to your firewall's allowlist, so your endpoint accepts the incoming POST requests. You'll find it in External connections & IP allowlist.

Create the webhook

In Admin → Integrations → Data Pipelines (Out), click New webhook. Give it a title, choose the surveys it should cover — search by survey or workspace, or tick a workspace to select all of its surveys — and enter your payload URL (it must use HTTPS). Add any custom headers your endpoint needs, such as an authentication token.

Trigger and verify

Complete one of the surveys to fire a delivery, then open the webhook's history to confirm receipt and debug any failures — every delivery is recorded there.

One webhook, many surveys

Webhooks that send to the same endpoint with exactly the same settings are shown as one row, listing the surveys they cover. From that row you can:

Edit it once for every survey. A change to the title, URL, headers or the Active switch applies to all of its surveys together — either every survey is updated or none is, so no survey is ever left sending to an old address.
Add or remove surveys. Open the webhook and change its survey list; newly added surveys start sending with the webhook's current settings.
Delete it. Deleting stops deliveries for every survey it covers.

Changes take effect from the next completed response.

Why two webhooks might not merge

Two webhooks appear as separate rows whenever anything about them differs — a header value, the title, the URL, or one being active and the other not. Make their settings identical and they are shown as one.

For the full details, see Read more about webhooks.

Watch the delivery history

The webhook's history shows every delivery attempt, newest first — across all of its surveys, with the survey each delivery came from. Open a delivery to see the exact request we sent and the response your endpoint returned, so you can confirm each completion arrived and quickly diagnose anything that didn't land.

Not the same as bringing recipients in

Webhooks are data out — they push completions to your systems. If you instead want to feed recipients or contacts into a survey campaign, that's a different feature: see data bridges.

Coming soon

More ways to get your data out are on the roadmap:

Automation platforms Coming soon — connect to Zapier, n8n and Make to trigger your own workflows.
Scheduled exports Coming soon — recurring exports to a BigQuery pipeline, Google Cloud Storage, Azure Blob Storage, Amazon S3 or an SFTP export.

Integrations

The overview of inbound sources and outbound pipelines.

Data Warehouse

Query your full dataset and sync it to your own database.

Data sources (in)

Connect external sources to ingest customer feedback into e-satisfaction.

Data bridges

Bring recipients into your survey campaigns — the inbound counterpart to webhooks.

External connections & IP allowlist

The IP addresses webhooks and data bridges connect from, for your firewall.