ServiceNow AI agents as secondary agents
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 , 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.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.