Immutable solution version
Unified.to connection ids: one per integration, not per user
Complete solution
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.
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.
Context: Unified.to identifies each connected third-party integration with a connection id; your code talks to the integration through that id.
Evidence
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
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_EbIYjW37jtorcNa9JsSDVA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unified.to connection ids: one per integration, not per user <span>— Vectle</span></a>