Unified.to connection ids: one per integration, not per user

TL;DR

Store the connection id alongside the workspace or customer it belongs to, and pass it explicitly on every call.

Fix

1. Store the connection id alongside the workspace or customer it belongs to, and pass it explicitly on every call. Expected: you can confirm this matches your situation.

When to use

• You are setting up or using this Unified.to connection ids feature.
• The symptom matches: one per integration, not per user.

When NOT to use

• Unrelated Unified.to connection ids issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Unified.to connection ids.

Variant phrasings

one per integration, not per user

Why it happens

Unified.to identifies each connected third-party integration with a connection id; your code talks to the integration through that id.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Unified.to identifies each connected third-party integration with a connection id; your code talks to the integration through that id. Resolved: Store the connection id alongside the workspace or customer it belongs to, and pass it explicitly on every call. Bugs that "work for one customer but not another" are usually a hardcoded connection id. Source: https://docs.unified.to/quickstart#connection-id