Opens in a new tab

How integrations work

Integrations are how you keep total control without living only inside InProQu. You connect your accounts. InProQu stores secrets encrypted and calls the provider on your behalf. You pay the provider directly (BYOK). InProQu does not resell their API.

Integrations in the sidebar → find a card → Connect. The card says Connected when it worked. A platform admin can hide a provider for the whole deployment. If a card is missing, ask them.

Auth types

TypeWhat you doExamples
OAuthSign in at the providerGmail, Slack, Dropbox, Salesforce, Google Contacts
API keyPaste a tokenHubSpot, Stripe, Claude, Twilio
Signing secretInProQu gives you a secretIncoming Webhooks
Scheduling linkPaste a public booking URLCalendly, Cal.com
NoneBuilt-in UICSV client import

Raw secrets are not shown again after save. Disconnect and reconnect to rotate a key.

What each family is for

FamilyJob in your workspace
EmailSend from Share
CRM and contactsPull (and optionally push) people into Clients
Import and exportCSV in; Sheets / Airtable out
StoragePDF copies + browse files in blocks
MediaStock photos, video browse
MessagingAlerts in Slack, Telegram, Teams, …
ProjectsTask / card after they accept
SchedulingBook a call on the public page
SigningDropbox Sign (DocuSign coming soon)
PaymentsCheckout on the link
AI providersDraft and chat keys
Analytics and live chatPixel / Intercom on /p/…
WebhooksForm / agent → client + draft; events out to Zapier

After they accept

When a client accepts, connected tools can run without you clicking again:

If connectedWhat happens
Google CalendarFollow-up event
Asana, ClickUp, Monday, Trello, JiraProject / task / item / card / issue
Stripe / PayPal / PayMongo / MayaPay is already on the page (accept is not required to pay)
Dropbox SignE-sign flow when the doc requires signature
Xero / QuickBooksDraft invoice: coming soon
Thank-you templateEmail the client if you have their address

You still Convert by hand (or auto-ack on paid) when you want an invoice or receipt in InProQu.

After they view or you share

Messaging apps and outbound webhooks (Team+) can fire on view, share, and accept. Payloads include source: "inproqu".

Plans

Most Connect cards work on trial and Pro. These need a higher plan:

FeaturePlan
Workspace SMTPPro+
Custom share domainPro+
Incoming webhooks, Zapier / Make / n8n catch, shared templatesTeam+
Knowledge catalog, SSO, workspace chromeBusiness

Rules that keep you in control

  1. Intake never auto-sends. Webhooks and forms create a draft.
  2. CRM push is off by default. Pull sync does not write back unless you enable push.
  3. Mute on one document stops alerts for that link only.
  4. Staff preview is not a client view. Messaging should not fire for your own Preview.
  5. Disconnect anytime. The document blocks stay; pickers just lose browse.

If Connect fails

  • Confirm the card is still enabled.
  • OAuth: the redirect must be exactly {your-app-url}/api/integrations/oauth/callback.
  • API key: check scopes (HubSpot contacts.read, Airtable schema write, Stripe webhook URL).
  • Webhooks from Stripe / Dropbox Sign need a public app URL.