Integration Activation Guide
Use this guide when you are setting up Enterpret integrations for the first time or deciding which integration path to use.
Enterpret integrations bring customer conversations, feedback, metadata, users, accounts, reports, alerts, and product workflows into one workspace. Most setup questions come down to four decisions:
What are you trying to bring in or send out? Feedback, user/account data, warehouse data, reports, alerts, or product work.
Is there a native integration? Use native integrations first when available.
If not native, what bridge path fits? Webhook, SFTP, file upload, Snowflake/warehouse, or Export API.
How will you validate first value? Confirm records, fields, user/account links, and expected counts before scaling the integration.
Who can manage integrations? Integrations can be controlled only by admins of an organization inside Enterpret.
Choose the right integration path
If you need to… | Use this path | Setup owner | Related article |
Ingest support tickets, reviews, calls, surveys, or CRM records | Native feedback integration | Workspace admin + source admin | Source-specific integration article |
Ingest custom feedback from an internal system | Webhook or SFTP | Engineering / Data | Webhook Integration, SFTP Integration |
Bring user/account context for segmentation | User & Account sync | Data / RevOps | Syncing Users and Accounts |
Send reports or alerts to Slack | Slack notification integration | Workspace admin + Slack admin | Slack Integration / Enterpret for Slack |
Create product work from feedback | Jira or Linear outbound integration | Product Ops / Eng Ops | Jira, Linear |
Export processed Enterpret data to a warehouse | Export API | Data / Engineering | Export API 2.0 |
Two types of integrations
Inbound integrations bring data into Enterpret. Examples include support tickets, app reviews, survey responses, Gong calls, Slack conversations, Salesforce records, Snowflake data, webhooks, SFTP, and file uploads.
Outbound integrations send data or work out of Enterpret. Examples include Slack reports and alerts, email reports, Jira, Linear, webhooks, and the Export API.
Two types of inbound integrations
Pull-based integrations pull or sync data from selected sources into Enterpret after authorization and configuration. Most native integrations are pull-based.
Push-based integrations let your team send data to Enterpret. Use these for custom sources, unsupported systems, warehouse workflows, or cases where you want to decide exactly what data gets sent.
Before you connect an integration
Before connecting a source, align on these questions:
Source: Which system contains the feedback or metadata?
Scope: Which objects, channels, surveys, tables, files, or fields should Enterpret ingest?
Feedback fields: Which fields contain direct customer language?
Metadata fields: Which fields should be used for filtering, grouping, segmentation, attribution, or routing?
Identifiers: Which user ID, account ID, email, domain, or source record ID links feedback to customers?
Volume: Do you need filters or sync conditions before data is ingested?
Owner: Who can authorize the source and who can validate the data?
Control volume before ingestion
If you only want certain records in Enterpret, configure the source as narrowly as possible before data starts flowing.
For Salesforce or HubSpot, choose the right primary object and fields, then use sync conditions where supported.
For Slack, choose only the channels that should be treated as feedback sources.
For Webhook, SFTP, warehouse, or file-based sources, filter rows before sending them to Enterpret when possible.
For user/account sync, include the identifiers and metadata fields needed for segmentation and linking.
This helps reduce noise, manage feedback volume, and make the first analysis more useful.
Validate first value
After setup, validate a small sample before inviting more people into the workflow.
Confirm expected records appear in Enterpret.
Check that customer-language fields are treated as feedback.
Check that metadata fields are available for filtering or segmentation.
Confirm user/account links work for a few known examples.
Compare counts against the same object, channel, field scope, and date range in the source system.
Save two or three safe source-record examples in case support needs to investigate.
Integration health
Enterpret monitors active integrations for freshness and recency. If data appears stale or incomplete, first check the integration details page, the selected scope, and the source-specific setup article.
If an integration is connected but expected data is missing, see My integration is connected — why is data missing or counts different?.
Note: Since the October 2025 Enterpret 2.0 update, integrations are accessed from the left sidebar navigation instead of under the profile menu.
Frequently asked questions
Does connecting an integration mean data starts flowing immediately?
Not always. Authorization is only one step. Some integrations also require selecting objects, fields, channels, sync conditions, and feedback-vs-metadata fields before ingestion starts.
Who should be involved?
Usually an Enterpret admin, the source-system admin, and sometimes a data or engineering teammate for custom, warehouse, webhook, SFTP, or identity-mapping work.
What should I validate before inviting the broader team?
Validate a small sample of records, expected fields, date ranges, source counts, and user/account matching.
What if my source is not supported natively?
Use Webhook, SFTP, file upload, or a warehouse-based path when a native integration is not available. If you need processed data out of Enterpret, use the Export API.