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

# Connect Biqli to Zapier

> Connect one Biqli workspace to Zapier triggers and actions.

The official Biqli Zapier integration lets a Zap receive workspace events and
create, retrieve, update, upsert, or delete links. It can also record attributed
lead and sale events.

## Connect a workspace

1. Add a Biqli trigger or action to a Zap.
2. Select **Connect a new account**.
3. Continue to Biqli and sign in when prompted.
4. Review the requested permissions and select the intended workspace.
5. Approve the connection and return to Zapier.
6. Confirm Zapier labels the connection with the selected workspace.

Each Zapier connection belongs to one workspace. Create another connection
when a Zap needs a different workspace.

Biqli credentials are handled by the official OAuth connection. Never paste a
client secret, access token, refresh token, or workspace API key into a Zap
field.

## Reconnect after permissions change

Older connections can keep the scopes approved when they were created. If a
new action reports a missing permission, reconnect the Biqli account in Zapier
and approve the current scope set. An existing access token cannot add scopes
silently.

## Instant triggers

Biqli supports triggers for link creation, updates, deletion, clicks, leads,
and sales. Zapier creates a dedicated subscription when the Zap is enabled and
removes that subscription when the trigger is disconnected.

Webhook delivery is at least once. Zapier and downstream steps should use the
event ID when they need deduplication.

## Actions

Available actions can create, retrieve, update, upsert, and delete links, and
track leads or sales. The connected workspace, its plan, the approving user's
current role, and API quotas still apply.

Use a stable external ID for upserts and stable idempotency values for
conversion actions so retries do not create duplicate business events.

## Disconnect

Remove the Biqli account from Zapier when it is no longer used. Revocation
invalidates the connection and removes its Zapier-owned webhook subscriptions.
Links and conversions already stored in the workspace remain available.

## Troubleshooting

| Symptom | Resolution |
| :- | :- |
| Zapier shows the wrong workspace | Create or select a separate connection for the intended workspace. |
| An action reports a missing scope | Reconnect and approve the current permissions. |
| Access is rejected after a role change | Restore the required workspace permission or reconnect as an authorized member. |
| A trigger no longer receives events | Confirm the Zap is enabled, reconnect the account, and recreate the trigger subscription. |
| A request is rate limited | Let Zapier retry after the returned delay and reduce task concurrency. |

For the dedicated endpoint contracts, read the
[Official Zapier integration API](/docs/api-reference/integrations/zapier).