Analyze External Integration Architectures

1. Researches the integration approach on its own and writes it up as an artifact.
2. Reads any reference material the user supplies and compares it with its own research. It lists points of agreement, gaps and items to scrutinize.
3. Pulls data from reference files and builds an integration scoping document as an HTML artifact, in one case for a MuleSoft integration.
4. Rebuilds the artifact when the user changes which sources to use. It then answers detailed follow-up questions and checks the domain lists.
5. Advises on network security for an org-to-org Bulk API integration, covering Hyperforce IP security, VPN limits and mTLS. It then checks its claims against Help articles.

The features that come up most are Event, the Agent API, External Client Apps, Change Data Capture and the Composite API. Once an option is chosen, the write-up usually continues in Document Technical Solution Designs.