Business Application Integrations

Connect the business apps your team already works in, such as your CRM, your accounting system or your web analytics. Querri loads their records into your Library as sources you can ask about.

Supported apps

A business app connects in one of two ways. Either you sign in with the app and approve access, or you enter a key or token the app gives you.

App	How it connects	After connecting	Category
Salesforce	Salesforce sign-in	Form: pick objects	CRM
HubSpot CRM	HubSpot sign-in	Nothing to set up	CRM
QuickBooks Online	Intuit sign-in	Nothing to set up	Accounting
Google Analytics	Google sign-in	Form: property and date range	Analytics
Google Drive	Google sign-in	File picker	Storage
Stripe	Stripe sign-in	Nothing to set up	Payments
Mailchimp	Mailchimp sign-in	Nothing to set up	Marketing, Email
Intercom	Intercom sign-in	Nothing to set up	Customer Support, Messaging
NetSuite	Token-based credentials	Form	ERP, Accounting
Mixpanel	Service account	Form	Analytics
Amplitude	API key and secret	Form	Analytics
Customer.io	App API key	Form	Marketing, Messaging
CharityTracker	API token	Form	CRM
Fluke eMaint	JWT token	Form	Business Applications, CMMS

A sign-in app appears only when Querri has set up that provider for your environment, so your list may be shorter. For databases and BigQuery, see Connecting Databases.

Connecting a sign-in app

1. Click Connect in the app rail to open Add data, and find the app under Connect a data source. Admins can also click Connect on it in Settings → Connectors.
2. The app’s sign-in window opens straight away. Sign in, and approve Querri’s access.
3. What happens next depends on the app:
   • HubSpot, QuickBooks, Stripe, Mailchimp and Intercom have nothing more to set up.
   • Salesforce and Google Analytics open a short form in the connector dialog. Salesforce asks which objects to sync, with the standard CRM objects already ticked. Google Analytics asks for a property and a date range. Save the form when you’re done.
   • Google Drive opens Google’s file picker, so you choose the files Querri can use.
4. Check that data loaded. Click the connector under Connectors in the Library’s browse panel. If it says the connector “is connected, but no data has loaded yet”, click Load data now to run a full sync. Only the connector’s owner can start a load.

If your browser blocks the sign-in window, Querri tells you. Allow pop-ups for Querri and click Connect again.

Closing the sign-in window before you finish leaves an unfinished connector behind. Admins see it under Cleanup in Settings → Connectors, marked Pending OAuth. Loading that page also clears your own unfinished attempts that are more than five minutes old.

Connecting an app with a key or token

1. Click Connect in the app rail to open Add data, and pick the app. The connector dialog opens on its Configuration tab.

2. Fill in the fields the app needs:

   App	Fields
   NetSuite	Account ID (sandbox accounts use a hyphen suffix, such as 1234567-SB1), Company URL (optional), Consumer Key, Consumer Secret, Token ID, Token Secret
   Mixpanel	Service Account Username, Service Account Secret, Project URL (Querri reads the project ID from it)
   Amplitude	API Key, Secret Key, Data Region (United States or European Union)
   Customer.io	App API Key, Data Region (Global (US) or European Union)
   CharityTracker	Network Subdomain, API Token
   Fluke eMaint	Product URL (your eMaint domain, without https://), JWT Token, Page Size (100 to 10,000; default 10,000)

   Most fields have a hint that says where to find the value in the app’s own settings.

3. Click Save. There’s no separate test step: Querri checks the credentials with the app first, and creates the connector only if they work. If the app rejects them, nothing is saved and the dialog shows the reason. If they work, the dialog closes and a message says the connector is connected.

4. Saving doesn’t load any data. Click the connector under Connectors in the Library’s browse panel, then click Load data now. Only the connector’s owner can start a load.

Pressing Enter anywhere in the dialog saves it, so fill in every field first.

Where the data goes

A new connector lands in the workspace you’re in if you’re a member of it, and in your private workspace otherwise. The app’s records arrive in the Library as sources. See Sources and connectors and Workspaces and privacy.

Querri copies app data into its own storage and answers from that copy. What you see is as fresh as the last sync.

Keeping app data fresh

• Schedules, on the connector’s Schedule tab, refresh data on a timetable. Only the owner can set them up. Use Full Refresh for most apps; Salesforce and NetSuite also support Incremental.
• Load data now, in the connector’s Library view, runs a full sync while nothing has loaded yet. Only the owner can start it.
• Re-sync now, in the connector’s right-click menu in the Library, asks for an incremental sync. Salesforce and NetSuite fetch only what changed since the last sync; apps that don’t track changes reload everything.

Scheduled syncs use credits when they run. Syncs you start by hand don’t. See Sync Scheduling and Credits.

When sign-in expires

If an app’s access expires, opening the connector shows Connection Failed with “Your authentication has expired. Please reauthenticate to continue.” Click Reauthenticate and sign in again. In the Library’s connector panel, the status reads Reauthentication needed.

Don’t disconnect and reconnect to fix it. Disconnecting deletes the data the connector synced.

Disconnecting an app

Open the connector and click Disconnect, followed by the connector’s name, at the bottom left of the dialog. Querri asks you to confirm, because this deletes the connector, the sources it synced, and everyone’s access to them.

To remove Querri’s access on the app’s side too, remove Querri from the connected apps in that app’s settings.

Troubleshooting

The sign-in window doesn’t open. Allow pop-ups for Querri in your browser, then click Connect again.

Nothing arrived after connecting. Click the connector under Connectors in the Library’s browse panel. If it says no data has loaded yet, the owner can click Load data now. If some records are still missing afterwards, check that the account you signed in with can see them in the app.

The key or token was rejected. The dialog shows the reason the app gave. Check the value, and for Amplitude and Customer.io, check the Data Region too.

A schedule stopped running. A schedule turns itself off after three failed runs in a row. Expired sign-in is a common cause. Fix it, then switch the schedule back on. See Sync Scheduling.

Next Steps

• Salesforce and HubSpot CRM
• QuickBooks Online and NetSuite
• Google Analytics and Google Drive
• Managing Connections: change, refresh and remove connectors
• Data Connectors Overview