ReferenceIntegrations

Integrations A–Z

Every tool Adduce reads from or writes to, what each one carries, how often it runs, what it needs from you, and whether it is live yet.

Twenty-five integrations, in one table: nineteen sources Adduce reads from and six destinations it writes to. Three of them cannot be chosen yet. This page names what each one carries and what it needs; the Connect page behind each name is where the setting up is written down.

Every source and destination

Sources sync once a day at 03:00 UTC, and Sync now on a source's own page runs one immediately — except call transcripts, which you upload rather than sync. Destinations have no schedule: each writes when you press something, or when the event it listens for happens.

ToolDirectionWhat it carriesCadenceWhat it needsStatus
AmplitudeSourceEvent trends, cohort retention, the funnels you define, and replay summaries behind a drop-offDaily, or on demandRegion, API key, secret keyLive
App Store reviewsSourceWritten reviews from the storefronts you chooseDaily, or on demandYour app's ID and countries. No credentialBeta
Azure Application InsightsSourceAlert rules that fired this week, and the day's exception groupsDaily, or on demandTenant, client ID and secret, subscription, resource group and nameBeta
Call transcriptsSourceFiles you upload, read as speaker turnsWhen you uploadA name for the collection. No credentialLive
CloudWatchSourceAlarms that are firing, and the errors that repeat in your logsDaily, or on demandRegion, access key ID and secret, log groupsBeta
DatadogSourceMonitors that are alerting, and error lines per serviceDaily, or on demandSite, API key, scoped application keyBeta
DelightedSourceNPS, CSAT and CES survey responsesComing soon
Firebase CrashlyticsSourceCrash and freeze groups from the last thirty daysDaily, or on demandCloud project, BigQuery dataset, service account keyBeta
GitHub IssuesDestinationOne issue per theme, with its numbers and quotesOn your clickFine-grained access tokenBeta
GongSourceRecorded calls, as transcripts with each speaker markedDaily, or on demandAPI base URL, access key and secretBeta
Google AnalyticsSourceTraffic trends, channel mix and landing pagesDaily, or on demandProperty ID, service account keyBeta
Google Play reviewsSourceReviews from your Play listingComing soon
HubSpotSourceLost-deal reasons, with the deal valueComing soon
IntercomSourceClosed conversations and tickets, in the customer's wordsDaily, or on demandRegion, access tokenLive
JiraDestinationOne issue per theme, in the project and type you chooseOn your clickSite URL, account email, API tokenBeta
LinearDestinationOne issue per theme, in the team you chooseOn your clickPersonal API keyBeta
NotionDestinationA brief as a page; publishing again updates itOn your clickIntegration secret, and a parent page shared with itBeta
Outbound webhooksDestinationSigned JSON when a theme changes or a brief is publishedOn the eventAn HTTPS endpoint of your ownBeta
PagerDutySourceIncidents your team declared, and how long each ranDaily, or on demandRead-only API key, region, servicesBeta
PostHogSourceSurvey answers, and your funnel and retention resultsDaily, or on demandAPI host, project key, read-scoped personal key, project IDLive
SentrySourceError issues weighted by the people they hit, and in-app feedbackDaily, or on demandOrganisation slug, auth tokenLive
Slack channelsSourceSettled conversations in the channels you listDaily, or on demandBot token, and the channels to readBeta
Slack, the Adduce appDestinationAnswers in the thread you asked in, plus digests and alertsOn the eventA workspace install, and a channelBeta
TypeformSourceThe free-text answers to the forms you chooseDaily, or on demandData centre, personal access token, formsBeta
ZendeskSourceSupport tickets, in the customer's own wordsDaily, or on demandSubdomain, admin email, API tokenBeta

What the statuses mean

Status is about how far a connector has been proven, not about how well it works. Only Coming soon stops you choosing something.

StatusWhat it means
LiveCarries data and has run against real customer accounts
BetaBuilt and carrying data, but not yet proven against a real customer account. A source in beta carries a Beta badge on its tile in the picker and is chosen the same way as any other; destinations have no tile, so a destination's status is stated here and nowhere in the app
Coming soonCannot be chosen. The tile is in the picker and is not selectable, and there is no Connect page for it yet

Two of the statuses above are an assessment rather than a record. Linear, Jira, GitHub Issues and outbound webhooks are marked beta in the connector catalog the public site reads. Notion and the Adduce app for Slack are in no catalog at all, so their Beta is Adduce's own reading of the same test: built and carrying data, not yet proven against a real customer account.

Two more differences are worth knowing before you plan around this table.

  • Direction never reverses. A source is only ever read; a destination is only ever written to. Closing an issue in your tracker changes nothing in Adduce, and nothing a destination holds is read back in.
  • Sources belong to a project; one destination does not. Every source and every destination is set up per project, except the Adduce app for Slack, which is connected once for the whole workspace.

On this page