Connect an agent to the right app and scope.

Start with the ERP.AI platform reference for authentication and supported resource procedures. Then open For your agent on the application page. The app-specific guide describes the business model and points to the appropriate reference material.

Follow the current setup instructions for the environment you intend to use. Review installer or skill setup instructions before executing them. The public marketing site and the authenticated application API are different surfaces, so use the API origin identified by the current guide.

Sign in to the intended organization and create an API key through the supported account settings when the integration requires one. Configure the client according to the current platform reference. API authentication uses a bearer credential; keep it in the supported local or secret configuration.

Never place a key in a public page, shared document, workflow definition, committed repository, or support message. Review the permissions assigned to the caller and the specific app resources it needs.

Use authenticated app discovery from the current reference and identify the app available in the selected organization. Use its actual app identifier. A catalogue slug such as crm-for-b2b describes a public product route; it is not your organization’s app ID.

Inspect the app and schema before asking the agent to create or change records. This lets it use the actual tables, fields, relationships, and permissions rather than assuming that every installation has the same configuration.

Ask for a small, permitted read with a clear expected result. Confirm the returned app and records. If the task needs writes, use a non-sensitive test record, a precise change, and the approval your operating policy requires.

Check the result in the application and review any downstream workflow or external effect separately. If access fails, use the troubleshooting guide to separate authentication, app context, and permission issues.