--- sourceDocument: Brazil Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # ServiceNow AI agents as secondary agents # ServiceNow AI agents as secondary agents {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of ServiceNow AI agents as secondary agents ServiceNow enables integration of its AI agents as secondary agents within other agentic AI systems such as Google Cloud or Azure OpenAI by using the Agent2Agent (A2A) protocol. This allows ServiceNow AI agents to function alongside external AI platforms, facilitating advanced multi-agent workflows. After creating an AI agent in AI Agent Studio, admins can obtain an Agent Card URL for easy access and management. Show full answer Show less The execution endpoint for invoking the ServiceNow AI agent follows a specific URL format and supports authentication via OAuth or API keys, which apply to both agent discovery and execution. Administrators can monitor active conversations and verify agent execution details through the Execution Plan table, which logs prompts and conversation objectives from external platforms. ## Key Features * **Discoverability of ServiceNow AI Agents:** On the AI Agent Studio Settings page, under External AI Agents \> Discoverability, you can enable third-party platforms to access ServiceNow AI agents by toggling the appropriate setting. * **Communication Modes:** Support for both synchronous and asynchronous communication between external AI agents and ServiceNow AI agents. Asynchronous mode requires setting up a callback URL for push notifications. * **Callback URL Management for Asynchronous Communication:** You register callback URLs in the External Agent Callback Registries table, which automatically creates associated connection and credential alias records. This setup enables secure and verified asynchronous interactions. * **Authentication:** Use OAuth or API keys consistently for both agent discovery and execution processes, ensuring secure integration. * **Monitoring and Troubleshooting:** The Execution Plan table provides visibility into ongoing conversations and execution status, aiding in operational oversight and debugging. ## Practical Application for ServiceNow Customers By leveraging this integration, ServiceNow customers can expand their AI capabilities by combining ServiceNow AI agents with other AI platforms, enabling richer, multi-agent interactions. This is particularly useful for organizations seeking to unify AI-driven workflows across heterogeneous environments. Enabling discoverability and choosing the appropriate communication mode ensures seamless interoperability. The asynchronous communication setup supports scalable and event-driven interactions, while synchronous mode facilitates real-time exchanges. Administrators benefit from streamlined management through the Agent Card URL and comprehensive monitoring via the Execution Plan table, enabling efficient control and troubleshooting of AI agent activities. Integrate ServiceNow AI agents into other agentic AI systems, such as Google Cloud or Azure OpenAI. ## Enabling discovery of ServiceNow mobile agents In AI Agent Studio, on the Settings page, under External AI AgentsDiscoverability, you can enable the discovery of ServiceNow AI agents to use on other AI platforms. To do so, toggle Allow third party to access ServiceNow AI Agents. You can also choose between Synchronous and Asynchronous communication between your external AI agent and the agentic AI provider. ## ServiceNow AI agents as secondary agents overview You can connect your ServiceNow agent to other agentic AI model providers using the Agent2Agent protocol. After creating your AI agent in AI Agent Studio, you can point to the Agent Card URL that is displayed for secondary agents for easy access so the admins can view, copy, and consume the URL. The endpoint to point to for the actual execution of the AI agent is in the format {{instance}}.service-now.com/api/sn_aia/a2a/v2/agent/id/{{agent-id}}. You can use the same OAuth or API key for authenticating the agent discovery and the agent execution. To verify that your AI agent is running from the ServiceNow side, during a conversation with the AI agent, you can go to the Execution Plan \[sn_aia_execution_plan\] table. From the Execution Plan table, you can identify the execution plan based on the Objective field that contains the prompt from the conversation on the other platform. For more information about sample payloads for Google A2A with ServiceNow AI agent as Secondary agent, see [Sample payloads for Google A2A](https://www.servicenow.com/community/now-assist-articles/sample-payloads-for-google-a2a-servicenow-as-secondary-agent/ta-p/3451904). For more information about setting up instructions for your ServiceNow AI agents as secondary agents (acting as A2A server), refer to [Authentication for Google A2A - ServiceNow as Secondary Agent](https://www.servicenow.com/community/now-assist-articles/authentication-for-google-a2a-servicenow-as-secondary-agent/ta-p/3446091). ## Asynchronous connection Asynchronous connection involves communication where the sender and receiver don't have to be active simultaneously unlike the synchronous communication mode. To establish asynchronous connection, you must obtain a callback URL for push notifications to function. Once you have obtained a callback URL, you must create a record on the External Agent Callback Registries \[sn_aia_external_agent_callback_registry\] table. Go to the table, select New, and enter the callback URL. Save the record. Once you save the record, a Connection \& Credential Alias \[sys_alias\] record is created for you. To add authentication, you can open the Connection record associated with the sys_alias record and add a credential to the Credential field. When the record is created, you can go back to the External Agent Callback Registry record you created and select Verify URL to test the connection works as expected. *[\>]: and then