Integration Hub Operations
Configure APIs, map records and review durable integration jobs.
Open interactive lesson and quizWhat you will learn
- Distinguish configurable APIs from native connectors
- Configure secure operations and mappings
- Review failures without duplicating remote writes
Your business needs to synchronize a custom service with validated SupaChrome records.
Lesson 1
Connection status and credentials
Configured means settings are saved. Connected means a provider request has succeeded; it does not certify every provider feature. Credentials remain encrypted and scoped to the BU and connection. OAuth authorization reuses the existing BU identity and permissions.
Lesson 2
Mapping and reliable processing
JSON imports use the existing validated create/upsert service with external IDs. Jobs retain deduplication keys, lease tokens and retries. Changed mappings require a fresh run. Ambiguous mutations enter Review unless the provider endpoint supports idempotency. Unattended jobs require the existing signed scheduler.
Lesson 3
Developer access
The versioned REST facade uses existing OAuth tokens, scopes, permissions and MCP tool approvals. The API Management area also preserves existing object ingestion APIs. Provider-specific modules and arbitrary cross-module CRUD are not implied by the universal request transport.
Lesson 4
Choose and verify a provider
Open the marketplace and review supported actions before entering credentials. Authorize Salesforce or QuickBooks before running their provider check. HubSpot, Slack, Stripe and Razorpay use provider-specific credentials. Teams, Zapier, Make and n8n verify outbound acceptance with a controlled workflow run. Shopify and WooCommerce stay in SupaCommerce External stores. A verified request does not prove a downstream sync, and providers marked Not yet supported do not have native setup.
Lesson 5
Bring external purchases into Orders
Use the native external-store connection for Shopify and WooCommerce. Send other site orders through the Commerce ingestion API or validate a CSV in Data Handler. Use the same source and stable external ID on retries; do not import the same sale through two channels. Stock, order and payment have separate checks.
Lesson 6
Request a governed deletion
In an object list, choose Select records to delete. In Postman, authorize records.delete, send explicit IDs and the object API name to DELETE /api/v1/records/{object}, then review the approval. A 202 response means queued. Preserve order and financial records through their normal cancellation and reversal actions.
Lesson 7
Operate and troubleshoot synchronization
Open Sync Manager to run a saved operation or pause a schedule. Logs filters job history by Queued, Processing, Succeeded, Retry and Review. No jobs means no execution is recorded. Inspect the destination record and external ID after success. Before replaying an ambiguous write, verify the provider outcome to avoid duplicate transactions. Mobile navigation uses the section selector.
Practice · Validate a JSON integration
- Create an HTTPS API connection using test credentials
- Save a GET JSON import operation with an external ID and field mappings
- Run the operation and review Logs
- Verify permission failures and idempotent retry behavior before enabling a schedule