> ## 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.

# Provider Setup Playbooks

> Provider-by-provider setup and validation flows for integrations, webhooks, and automation destinations

# Provider Setup Playbooks

This page gives practical setup flows for the major integration providers from a workspace operator perspective.

## Common prerequisites (all providers)

1. Confirm your plan includes integrations and related modules.
2. Confirm workspace operator has correct permissions.
3. Define expected data flow before connecting:
   * inbound ingestion
   * outbound automation
   * both
4. Prepare test data and a rollback plan.

## Stripe setup playbook

Primary use:

* ingest commerce and lifecycle outcomes for conversion/revenue workflows
* support payout/account flows where configured

Steps:

1. Connect Stripe integration from workspace integrations.
2. Confirm account/workspace mapping is correct.
3. Configure lifecycle and value mapping controls.
4. Send a Stripe test event.
5. Confirm converted event appears with correct status, value, and currency.
6. Confirm duplicate delivery handling is stable.

Constraints to validate:

* event status mapping (pending/approved/refunded style outcomes)
* currency normalization and finance reconciliation
* retry behavior does not duplicate conversions

## HubSpot setup playbook

Primary use:

* align lead and lifecycle signals with conversion reporting

Steps:

1. Connect HubSpot account.
2. Configure lifecycle/deal stage mapping.
3. Configure trigger events for desired conversion classes.
4. Send controlled lead-stage test event.
5. Validate resulting conversion status and customer stitching behavior.

Constraints to validate:

* stage mapping matches your sales process
* event naming and status are consistent

## Slack setup playbook

Primary use:

* outbound operational notifications

Steps:

1. Connect Slack workspace and authorize channel access.
2. Select notification categories and trigger rules.
3. Send a test notification from integration settings.
4. Validate channel delivery and message content quality.

Constraints to validate:

* no sensitive data leakage in outbound message templates
* channel and mention routing follows incident policy

## Shopify setup playbook

Primary use:

* ecommerce order and lifecycle ingestion

Steps:

1. Connect store and configure webhook/pixel-related settings.
2. Confirm store-level credentials and secret values.
3. Send test order/checkout event.
4. Validate event appears in Conversions/Events with expected mapping.
5. Validate customer stitching fields and value context.

Constraints to validate:

* order IDs are stable for idempotency
* refunds/reversals update analytics as expected

## Zapier and generic webhook automation playbook

Primary use:

* connect Linquid events to automation workflows and destination systems

Steps:

1. Configure destination URL and secret/token.
2. Select only required trigger categories.
3. Send test payload and verify downstream action.
4. Replay test payload to validate dedupe/idempotency downstream.
5. Confirm failure alerts and retry visibility.

Constraints to validate:

* destination latency does not create operational blind spots
* payload includes only required fields for the workflow

## Segment and event-forwarding setup playbook

Primary use:

* event fan-out into analytics/warehouse tooling

Steps:

1. Configure write key and forwarding settings.
2. Select event classes to forward.
3. Run test event from each required class.
4. Confirm destination receives expected normalized fields.
5. Confirm no duplicate inflation when retries occur.

Constraints to validate:

* forwarding scope is intentional
* customer identifiers are consistent across tools

## Validation routine after every provider change

1. Send one test event per enabled trigger family.
2. Verify event appears in expected Linquid UI surfaces.
3. Verify downstream destination behavior.
4. Verify retries and dedupe handling.
5. Capture a short change log entry for auditability.

## Failure triage matrix

| Symptom                         | Likely cause                          | First action                                     |
| ------------------------------- | ------------------------------------- | ------------------------------------------------ |
| Integration status stays error  | Token expired or auth scope invalid   | Reconnect provider and review scopes             |
| Events appear with wrong values | Mapping mismatch                      | Re-check field mapping and normalization         |
| Duplicate outcomes              | Missing idempotency handling          | Enforce stable event/transaction IDs             |
| No outbound payloads            | Trigger disabled or destination issue | Verify trigger enablement and destination health |

Related:

* `/user-guides/manual/ecosystem/workspace-integrations-reference`
* `/user-guides/manual/ecosystem/integrations-and-automation`
* `/user-guides/manual/ecosystem/integrations-and-webhooks-reference`
* `/user-guides/manual/data/conversion-tracking-setup-playbook`