​

Integrations and Webhooks Reference

This page describes integrations and webhook operations in user-operational language.

​

Integrations page operating model

The Integrations area typically has three modes:

• Available: browse installable providers
• Installed: inspect status and credentials for active installs
• Automation: define outbound event deliveries

​

Integration lifecycle statuses

Installed integrations move through statuses:

• active
• paused
• error
• disconnected

​

Integration categories

Common categories:

• payments/billing providers
• ecommerce providers
• CRM/marketing providers
• messaging and automation tools

Typical provider families in operations:

• Stripe for billing/commerce-linked flows
• Shopify for ecommerce signal ingestion
• HubSpot for CRM lifecycle context
• Slack for operational notifications and interactive workflows
• Zapier/webhook tooling for custom automation chains

OAuth-heavy providers commonly include Stripe Connect, HubSpot OAuth, and Slack OAuth flows. Shopify deployments can include pixel-style instrumentation alongside webhook ingestion. Shopify pixel deployments should be validated end-to-end against conversion attribution expectations.

​

Inbound ingestion patterns

Inbound flows may bring:

• conversion/order outcomes
• customer lifecycle changes
• interaction events for automation

Typical ingestion examples:

• Stripe/Shopify order and payment outcomes
• HubSpot lifecycle state changes
• provider-originated conversion signals tied to link/campaign context

​

Outbound delivery patterns

Outbound flows may push:

• conversion-related events
• workspace and link event payloads
• automation notifications

Common outbound trigger set:

• sale created
• lead created
• link clicked
• commission created

Inbound Stripe integration webhooks usually carry the highest billing/revenue impact and should be monitored closely.

​

Webhook surfaces in Linquid

User-facing webhook classes include:

• workspace-level webhook subscriptions
• link-level webhook subscriptions
• outbound integration webhook destinations
• webhook management and delivery-log troubleshooting workflows
• email-provider webhook handling (for example Resend delivery/bounce events)

​

Trigger families

Operational trigger families include:

• link lifecycle events
• conversion and sales events
• commission and payout events
• partner lifecycle events

​

Delivery reliability model

Key expectations:

• payload signing for authenticity
• retry model for transient failures
• delivery logs for troubleshooting
• test-send workflows before production rollout

​

Secret management

Best practice:

• rotate webhook secrets regularly
• isolate test and production delivery targets
• make receiver handlers idempotent

​

Workspace webhooks vs integration webhooks

Use workspace/link webhooks when you need direct event forwarding from Linquid operations. Use provider integrations when you need:

• provider auth lifecycle
• provider-specific mapping/configuration
• richer provider context for ingestion or delivery

​

Standard rollout sequence

1. Connect provider in a test workspace.
2. Confirm integration status is active and credentials are valid.
3. Validate first inbound/outbound test payloads.
4. Enable only required triggers.
5. Monitor first production-day delivery logs for retries or signature failures.

​

Troubleshooting checklist

If webhook automation appears inconsistent:

1. confirm integration status is active
2. confirm trigger subscriptions are enabled
3. confirm destination can accept signed payloads
4. review delivery logs and retry outcomes
5. validate workspace and feature gates

Related:

• /user-guides/manual/ecosystem/integrations-and-automation
• /user-guides/manual/workspace/security-and-compliance