Skip to main content

Integrations

Integrations shows external services for the active business, their connection states and the setup actions available to your account. Connected, Not connected and Coming soon mean different things. A successful authorization can still leave provider verification or feature-specific setup unfinished.

Connect a provider​

  1. Confirm the business and that you have permission to manage the integration.
  2. Open Integrations and find the provider.
  3. Read its current state and choose the available connection action.
  4. Review the requested provider permissions and use the intended business identity during authorization.
  5. Return to SRVZr and verify the connected identity. Open the feature that will use the connection and check its readiness there too.
ConnectionWhat to review
WhatsApp, Messenger and Instagram messagingThe connected business identity and the team's messaging setup.
StripeAccount verification, payment and payout readiness, and the relevant terminal or payment settings. Connection alone does not prove a successful payment.
e-TransferThe email customers send Interac e-Transfers to: your own verified deposit email (or a SRVZr Mail inbox). Forwarded deposit notices mark orders paid automatically. Money goes straight to you; it is not a card processor and SRVZ never holds the funds. See Take Interac e-Transfer payments.
QuickBooksA one-time accounting import with a switch date, explained below.
Bills by emailThe configured bills mailbox and actual recent bill results. See Bills for review and accounting steps.
Google My BusinessThe intended business profile and available listing/review actions.
Facebook, Instagram, YouTube, TikTok and XThe account selected for Content publishing and any provider-specific requirements.
SquareThe inspected card says Coming soon. Treat it as unavailable until an actual setup is offered.

The inspected test business had a connected bills mailbox and a recent bill. The other listed connections were not authorized during this review. Their setup controls do not establish live messaging, payment, posting or bank matching results.

QuickBooks Import​

QuickBooks Import moves accounting history from QuickBooks Online into SRVZr Books. It is a one-time move, not an ongoing two-way sync. The opening screen states that nothing in QuickBooks changes.

Use it when changing the system in which the business keeps its books. For example, a business can bring earlier accounting history across, then continue its new work in SRVZr from the chosen switch date. This is a bookkeeping migration decision, rather than an ordinary file attachment or a CSV upload wizard.

  1. Confirm that you have Manage books access and open Integrations → QuickBooks.
  2. Choose Connect QuickBooks Online and authorize the intended company.
  3. Review the connected company, country, currency and proposed switch date. Resolve any mismatch before proceeding.
  4. Read the import confirmation carefully. History before the switch date comes from QuickBooks; native SRVZr entries before that date can make way for the imported history. Check existing records and retain the exports you need before running the migration.
  5. Start the import only when those choices are correct. Follow the job's progress and review its record counts, warnings and any reported error.
  6. Review the accounting verification results, including the trial-balance comparison and any differences. A completed job is not, by itself, proof that every account reconciles. An unchecked or unavailable comparison is not a passing comparison.
  7. Inspect representative customers, suppliers, invoices, bills and balances in Books before relying on the migrated history.

The implementation imports supported accounts, customers, vendors, items, journal entries, invoices, credits, bills and vendor credits, then attempts its accounting comparison. Review the actual job result for what arrived; do not assume every QuickBooks feature or attachment is supported.

Disconnecting the provider does not remove already imported accounting records. Re-running an import is a separate consequential action: review its scope and existing job state before proceeding.

Verification boundary: the connection screen and implementation were reviewed. No external account was authorized, import started, switch date applied or balance comparison completed. No empty connection screen is presented as a successful migration screenshot.

API Integrations​

Use a Listings API key when another site or application needs the business's public services, events, menus and rentals. This key is scoped to listings; it is not a general-purpose grant to every customer, financial record or workspace action. Provider connections above use their own authorization flows.

  1. Open Assets in the intended business and find API Keys.
  2. Choose Generate API Key only when ready to create a live key. The action creates it immediately.
  3. Give the integration a recognizable name where the control allows it. Copy the key into the integration's private server-side configuration.
  4. Use the supported listings request with the x-api-key header. Keep the actual value out of public browser code, URLs, screenshots and documents.
  5. Inspect the returned services, events, menus and rentals and compare them with the intended public listings. A private or unpublished item should not be made public merely to fill an integration screen.
  6. Review the key's listed activity when troubleshooting. Revoke a key when access is no longer needed; dependent requests will need a replacement key.

The interface masks stored values but also offers a copy action. Treat every copied value as a credential, including after dismissing the initial reveal. Use separate keys for integrations you need to retire independently.

Verification boundary: key creation, listing filters and the request header were reviewed in the implementation. No key was generated, revealed, copied or revoked for this guide, and no authenticated listing request was executed. The guide intentionally contains no live credential or private API host.

Troubleshooting​

  • Connected identity is wrong: stop before using the feature and reconnect with the intended business account.
  • Provider is connected but work fails: check permissions, required verification and the feature's own status. Reauthorization does not resolve every setup problem.
  • QuickBooks job has warnings or differences: inspect the job details and affected accounts; do not treat “finished” as “reconciled.”
  • Listings are missing: check public visibility and publication state, the selected business and the key's validity before changing records.
  • Listings request is rejected: verify the header and key privately, and check whether the key was revoked. Never paste the credential into a support screenshot.

Stripe video tutorial​

How to connect Stripe in SRVZr (Setup and payment options)YouTube ↗

Related guides: Assets, Mail, Permissions and Settings.