> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linquid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace Integrations Reference

> Catalog, installation lifecycle, provider settings, inbound/outbound data flow, and operational runbooks

# Workspace Integrations Reference

This guide covers integration operations from the workspace settings and integrations pages.

## Integration lifecycle

Typical lifecycle:

1. Install/connect provider.
2. Configure provider settings.
3. Enable required triggers/subscriptions.
4. Monitor health and delivery.
5. Pause/disconnect when needed.

Common states:

* active
* paused
* error
* disconnected

## Supported provider classes

Common provider classes include:

* payments (for revenue/conversion ingestion)
* CRM systems (lead/customer sync patterns)
* ecommerce systems (order and lifecycle signals)
* chat/automation destinations (alerts and event forwarding)

## Workspace integrations page behavior

Typical capabilities:

* browse catalog
* open provider detail page
* connect/disconnect
* view installation metadata
* access provider-specific settings

## Provider settings reference

### Stripe

Common options include:

* conversion and lifecycle sync controls
* free-trial tracking toggles
* quantity/provisioned-seat tracking options

### HubSpot

Common options include:

* lead trigger event mapping
* lifecycle stage configuration
* closed-won stage mapping

### Slack

Common options include:

* workspace/channel authorization
* destination channel selection
* event notification routing

### Segment

Common options include:

* write key setup
* event forwarding and mapping behavior

### Shopify

Common options include:

* webhook URL verification
* webhook secret management
* store-specific event sync behavior

### Zapier / generic automation connectors

Common options include:

* webhook URL
* secret/token validation
* trigger event selection

## Webhook and signature operations

For inbound/outbound webhook-style integrations:

1. verify destination URL and TLS.
2. configure and securely store secrets.
3. verify signature handling.
4. test retries and idempotent receiver behavior.

## Data flow expectations

Typical integration outcomes:

* inbound conversion events become conversions/customers/events.
* outbound automations forward selected workspace events to external tools.
* analytics and reporting reflect ingested events after processing windows.

## Testing checklist by provider

1. Run test event end-to-end.
2. Confirm event appears in intended Linquid page/tab.
3. Confirm status/value/currency fields are correct.
4. Confirm retries do not create duplicate outcomes.
5. Confirm disabling integration halts new event sync.

## Failure scenarios and first actions

| Scenario                         | Likely cause                             | First action                                      |
| -------------------------------- | ---------------------------------------- | ------------------------------------------------- |
| Integration stuck in error       | Expired credentials or invalid mapping   | Re-auth and validate settings                     |
| Events received but wrong values | Field mapping mismatch                   | Re-check provider field mapping and normalization |
| Duplicate conversions            | Missing idempotency key                  | Enforce stable transaction/event IDs              |
| No outbound deliveries           | Trigger disabled or destination failures | Confirm trigger config and delivery logs          |

Related:

* `/user-guides/manual/ecosystem/integrations-and-automation`
* `/user-guides/manual/ecosystem/provider-setup-playbooks`
* `/user-guides/manual/ecosystem/integrations-and-webhooks-reference`
* `/user-guides/manual/data/conversion-methods-and-event-types-reference`