Connect a workspace
- Add a Biqli trigger or action to a Zap.
- Select Connect a new account.
- Continue to Biqli and sign in when prompted.
- Review the requested permissions and select the intended workspace.
- Approve the connection and return to Zapier.
- Confirm Zapier labels the connection with the selected workspace.
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
For the dedicated endpoint contracts, read the
Official Zapier integration API.

