Operate

Connect each tool once, with its own credential.

One integration carries its webhooks, its web API operations, its data types and its MCP server. Every agent and workflow uses it within the permissions you set.

Start free Book a demo

Free forever plan, no commitment, in your own cloud account.

Built from the real interface. Open the integrations view in the live demo. No sign-in.

acme / Integrations / Datadog OverviewWebhooksWeb APIsMCPAgents

Inbound

Webhook: monitor alertsVerified, recorded, stored as DatadogAlert on the owning stackenabled

Outbound

Web API: mute monitor, add tagCredential: external identity datadog-ro, tenant scopeenabled
MCP server: datadogTools for agents. Credential passed down, never stored in the agentenabled

Uses this integration

Agent: datadog-alert-triageRead-only. Reports cause, affected environments, next actioninstalled
Workflow: datadog-alert-responseFires on a high-priority delivery, runs the agent, posts to Slackinstalled

Permissions

Who can use itWorkspace payments, environment prod. Approval needed to mute.

Before and after

Before

  • A connector per tool, per team
  • API keys in CI variables and scripts
  • Agents with credentials pasted into prompts
  • Vendor data nobody can query later
  • Waiting on a vendor roadmap for your own tools

With Wayfinder

  • Webhook in, web API out, data type and MCP in one definition
  • Credentials as external identities, scoped and rotated
  • MCP credentials passed down to agents, never stored in them
  • Deliveries stored as typed, queryable data on the resource
  • Create your own from a template

How it works

Install or create

Enable a shipped integration such as Datadog, GitHub or PagerDuty, or create one from a template.

Give it a credential

An external identity for the web API, another for the MCP server. Scoped to a tenant or a workspace.

Use it everywhere

Workflows call its operations, agents use its tools, deliveries land as data.

In the product

acme / Integrations / Datadog OverviewWebhooksWeb APIsMCPAgents

Inbound

Webhook: monitor alertsVerified, recorded, stored as DatadogAlert on the owning stackenabled

Outbound

Web API: mute monitor, add tagCredential: external identity datadog-ro, tenant scopeenabled
MCP server: datadogTools for agents. Credential passed down, never stored in the agentenabled

Uses this integration

Agent: datadog-alert-triageRead-only. Reports cause, affected environments, next actioninstalled
Workflow: datadog-alert-responseFires on a high-priority delivery, runs the agent, posts to Slackinstalled

Permissions

Who can use itWorkspace payments, environment prod. Approval needed to mute.

What this shows

  1. Inbound: the webhook, verified and recorded, storing DatadogAlert on the owning stack.
  2. Outbound: operations and the MCP server, each with its own credential.
  3. Who uses it: the agent and workflow that became installable when this was enabled.

Components

Integration

Groups the pieces and gives them context. Shipped, or yours.

Webhook

An endpoint a vendor posts to. Verified, recorded, mapped to a data type.

Web API

Named, templated operations against an external API.

Data type

The schema a delivery is stored as, indexed and queryable.

MCP server

Tools for agents, registered per tenant with credential pass-down.

AI provider

Where inference comes from: Anthropic, Google, or your own.

Security and governance

Scoped credentials

Each credential is an external identity with a scope, a purpose and a rotation.

Credentials stay in the MCP server

An agent never sees the credential; the MCP server does.

Access per workspace

Who can use an integration is set per workspace and environment.

Every call logged

Every delivery and every call is a recorded invocation.

More of the platform

WorkflowsCloud resource plansRepo templateswayfinder.yaml and the CLIEnvironmentsAI agentsIntegrationsUpgrades and driftSecurity and governance

Connect your first tool today.

Start free, enable Datadog or GitHub, and watch the first delivery land.

Start free Book a demo