- Erste Schritte
- Benachrichtigungen
- Lizenzierung
- Fehlersuche und ‑behebung
- Codierungs-Agents
- Connector Builder
- Über Connector Builder
- Erstellen Ihres ersten Connectors
- Erstellen Ihres Connectors aus einer API-Definition
- Konfigurieren der Authentifizierung
- Verwenden von Variablen im Connector-Generator
- Aktivitätsdesigner
- Erstellen eines Triggers
- Globale Skripte
- Checkliste für den Connector Builder
- Erste Schritte
- Beispiel A: Erstellen Sie einen Connector aus einer leeren Canvas mit Authentifizierung mit persönlichem Zugriffstoken
- Beispiel B: Erstellen Sie einen Connector aus einer leeren Canvas mit API-Schlüsselauthentifizierung
- Beispiel C: Erstellen eines Connectors aus einer API-Spezifikation mit OAuth 2.0 Client-Anmeldeinformationenauthentifizierung
- Act! 365
- ActiveCampaign
- Active Directory – Vorschau
- Adobe Acrobat Sign
- Adobe PDF Services
- Agent 2 Agent - Preview
- About the Agent 2 Agent connector
- Agent 2 Agent authentication
- Agent 2 Agent events
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Defender for Cloud
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- Team AI – Vorschau
- Customer.io
- Database Hub
- Databricks-Agent
- Datadog
- DeepSeek
- Deputy
- Discord – Vorschau
- DocuSign
- Drop
- Dropbox
- Dropbox Business
- Egnyte
- Epic FHIR – Vorschau
- Eventbrite
- Wechselkurse
- Exchange Server – Vorschau
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Formulare – Vorschau
- Google Maps
- Google Tabellen
- Google Sprache-zu-Text
- Google Text-to-Speech
- Google Tasks – Vorschau
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- http
- HTTP-Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV – Vorschau
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- E-Mail (Mail)
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- MCP
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Azure Sentinel
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive und SharePoint
- Microsoft Outlook 365
- Microsoft Power Automate – Vorschau
- Microsoft Sentiment
- Microsoft Sentinel-Threat Intelligence
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- NVIDIA NIM
- Okta
- OpenAI
- OpenAI V1-konformes LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- Paypal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Agentforce & Flows
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center – Vorschau
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Apps - Preview
- UiPath Data Fabric
- UiPath Test Manager
- UiPath GenAI-Aktivitäten
- UiPath Orchestrator
- X (früher Twitter)
- Xero
- wassonx.ai zu senden
- WhatsApp Business
- WooCommerce
- Durchführbar
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho-Desktop
- Zoho Mail
- Zoom
- ZoomInfo
Agent 2 Agent authentication
Connect Integration Service to a remote Agent2Agent (A2A) agent by entering its service URL and the credentials for the authentication type the agent requires.
Each Agent 2 Agent connection points to one remote agent. Create a connection for every agent you want to call from Maestro.
Voraussetzungen
- The remote agent meets the remote agent requirements.
- The base URL of the agent, used as the Service URL. Enter the base URL only, without a path or a trailing slash. The connector adds the A2A paths, such as
/.well-known/agent-card.json, itself. - The credentials for the authentication type that the agent requires. The agent declares its supported security schemes in its Agent Card.
Authentifizierungstypen
All authentication types require the Service URL. The other fields depend on the authentication type.
| Authentifizierungstyp | Felder |
|---|---|
| Einfache Authentifizierung | Username, Password (optional), Authentication validation API (optional) |
| API-Schlüssel | Parameter name, Value, Add to (Header or Query, default Header), Authentication validation API (optional) |
| Persönliches Zugriffstoken | Token prefix (default Bearer), Token, Authentication validation API (optional) |
| OAuth 2.0: Autorisierungscode | Client ID, Client secret, Authorization URL, Token URL, Scope (optional) |
| OAuth 2.0: Client-Anmeldeinformationen | Client ID, Client secret, Token URL, Scope (optional) |
| OAuth 2.0-Kennwort | Client ID, Client secret, Authorization URL, Token URL, Username, Password (optional), Scope (optional) |
| OAuth 2.0 JWT Bearer | Client ID, Client secret, Authorization URL, Token URL, JWT base64 encoded key, Scope (optional) |
The following fields need more context:
- Parameter name: the exact name of the header or query parameter that carries the API key, for example
X-API-Key. - Token prefix: the prefix added before the token in the
Authorizationheader. Leave it empty if the agent expects the token without a prefix. - Authentication validation API: a relative path that returns a successful response when the credentials are valid, for example
/api/v1/me. - Scope: the OAuth scopes requested from the authorization server of the agent, as declared in its Agent Card. Separate multiple scopes with spaces or commas. Leave it empty to use the default scopes of the authorization server.
- JWT base64 encoded key: the Base64-encoded private key used to sign the JWT. Follow the instructions of your identity provider to generate and encode it.
Add the Agent 2 Agent connection
-
Wählen Sie Orchestrator im Produktstarter aus.
-
Wählen Sie einen Ordner aus und navigieren Sie dann zur Registerkarte Verbindungen .
-
Wählen Sie Verbindung hinzufügen aus.
-
To open the connection creation page, select the Agent 2 Agent connector from the list. You can use the search bar to find the connector.
-
In Service URL, enter the base URL of the agent.
-
Select the Authentication Type.
-
Enter the fields required for the selected authentication type.
Wenn verfügbar, wählen Sie das Menü neben einem Feld und dann Anmeldeinformations-Asset verwenden oder Orchestrator-Asset verwenden aus , um auf ein Orchestrator-Asset zu verweisen, anstatt den Wert direkt einzugeben. Weitere Informationen finden Sie unter Verwenden von Anmeldeinformationsassets für Verbindungen.
-
Select Connect.
The connection is created and named after the agent, as declared in the name field of its Agent Card.