Skip to main content
Forge integrations make external context and actions available to Chat and background workflows. A healthy connection is the first layer; each customer workflow must also have the right data, mapping, tools, Availability, and access.

​
Read a system’s settings

A connected system can expose: The available tabs differ by system.

​
Connected vs workflow-ready

Use this checklist before declaring a workflow ready:
  • the intended connection is active;
  • required data is present and current;
  • the relevant external account or tenant is mapped;
  • the needed tools appear in the catalog;
  • provider-specific limits are understood;
  • the tool is enabled for the intended surface;
  • the user role or background workflow has access;
  • read behavior was checked with a representative target;
  • every enabled write was tested and verified;
  • the human fallback is documented.

​
Map accounts carefully

An incorrect account mapping can point an otherwise valid tool at the wrong tenant. Confirm both the Forge account and the external identifier. Test a read-only query that returns recognizable, non-sensitive data before enabling write tools for account-scoped work.

​
Check sync and source freshness

If a record differs from the source system:
  1. confirm you are viewing the right organization and account;
  2. check connection and sync health;
  3. compare update timestamps when available;
  4. refresh or rerun the supported sync;
  5. verify the source provider;
  6. escalate persistent mapping or synchronization issues.

​
Understand provider coverage

One provider may support a synchronized record but not every interactive field, write action, attachment, or administration workflow. Keep unsupported provider-specific work in the source system. See the integration catalog and Availability and approvals.