SourceLace
Webhooks or A2A

A notification, or a task with an answer back.

Two ways let another system start a SourceLace agent. A webhook says "this just happened". A2A says "do this job and tell me how it went". Pick the one that matches what the other side needs.

Both run the agent as a person with that person's own access, and both keep every rule: shadow mode, approvals, limits, data protection and the audit trail.

The difference

Telling an agent, or asking one.

Webhook

A notification

A system calls the agent's start address, a web address SourceLace makes for it, the moment something happens: a priority 1 case is created, an invoice is paid, a file is shared. SourceLace checks who is calling, starts the agent, and answers with a quick "received". The result stays in SourceLace, in the run and the approvals inbox.

Use it when the other system only needs to say that something happened, or cannot speak A2A.

A2A

A task with an answer back

A2A (Agent2Agent) is an open standard for agents on different platforms to work together. An agent elsewhere hands your agent a job, such as "summarize the open escalations for this customer", and follows it: working, needs sign-in, needs a decision, then completed with the summary and a link to the run.

Use it when the other side needs the answer, needs to know where the job stands, or has to wait for an approval.

Side by side

How they compare.

A2A works both ways

Other agents call yours, and yours call theirs.

Your organization's callable agents are listed together in one agent catalog, so a partner's platform can find them all at once. Agents that are not callable do not exist to anyone outside. And your own agents can ask agents on other platforms for help, such as a partner's pricing agent.

  • Calling in. The owner turns on Callable by other agents. The other platform gets the agent's card: its name, a one-line description and how to sign in, never its instructions.
  • Calling out. An admin adds the other agent. Your agent can ask only the outside agents its setup names, and what it sends passes your data protection rules first.
  • Nothing leaves unseen. Messages to outside agents wait for a person's approval by default, showing exactly what would be sent and to whom.
  • Approvals stay home. An agent on another platform can never approve anything. A person does, in SourceLace.
An example each

The same company, three moments.

Webhook

A case lands

When a priority 1 case is created in the CRM, its automation calls the escalation agent's start address. The CRM only needs to say "this happened". The agent drafts the customer email and waits for approval.

A2A, calling in

A partner asks

A partner's procurement agent asks the renewals agent for next quarter's renewals, and waits for the list. It needs the answer, so it is a task.

A2A, calling out

Your agent asks

The renewals agent asks the reseller's quoting agent for a price on each renewal. Each question waits for the renewals manager's approval, so nothing leaves unseen.

Often used with webhooks

  • Salesforce
  • HubSpot
  • ServiceNow
  • Jira
  • Zendesk
  • Slack
  • Teams
Which to choose

Three questions.

  • Does the other side only need to say that something happened? Use a webhook. It works with any system that can call a web address, and many have a ready-made setup guide: see which systems can send events.
  • Does it need the answer, a status, or to wait for a decision? Use A2A.
  • Both? Use both on the same agent: a webhook starts it, and it asks outside agents for help while it runs.

See how agents start and work together.