Datadog (Independent Publisher)

[aaronmahbuild]

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I attest that I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

---

Datadog — Independent Publisher Connector

Overview

Datadog is a cloud-scale monitoring and security platform for infrastructure, applications, logs, and more. This connector enables Power Automate flows to interact with Datadog monitors, incidents, events, hosts, SLOs, and downtimes — powering alert routing, incident management, deployment coordination, and operational health reporting.

This connector provides action operations only. Polling triggers for monitors and incidents are planned for a future version.

Publisher

Aaron Mah

Operations (12 total)

Operation	Type	Description
List Monitors	Action	Retrieves a list of all monitors with optional filtering by name, tags, or state
Get Monitor	Action	Retrieves the details of a specific monitor by its ID
Mute Monitor	Action	Mutes a monitor to suppress alert notifications
Unmute Monitor	Action	Unmutes a previously muted monitor to resume alerts
List Incidents	Action	Retrieves a list of incidents sorted by creation date
Get Incident	Action	Retrieves the full details of a specific incident by ID
Create Incident	Action	Declares a new incident with title, severity, and commander
Update Incident	Action	Updates an existing incident's title, severity, or state
Post Event	Action	Posts a custom event to the Datadog event stream
Get Host Totals	Action	Returns total number of active and up hosts
List SLOs	Action	Retrieves all Service Level Objective definitions
Create Downtime	Action	Schedules a downtime to suppress alert notifications

Test Results

• 11/12 operations tested successfully in PA environment (1 known issue: updateIncident requires paid Incident Management seat)
• swagger-cli validate passed (exit code 0)
• 3 end-to-end scenario flows validated in Power Automate

Known Issues

• updateIncident returns HTTP 403 — requires Incident Management paid seat add-on. All other incident operations (create, get, list) work correctly. This is a Datadog plan limitation, not a swagger bug.

Test Tab — All Operations

Scenario Flows

Scenario 1: Periodic Monitor Alert Check
Recurrence → listMonitors → ForEach(getMonitor → Condition → Compose)

Scenario 2: Deployment Coordination
Recurrence → postEvent → Delay → listMonitors → postEvent → Compose

Scenario 3: Weekly Operational Health Digest
Recurrence → listMonitors + listIncidents + getHostTotals + listSLOs (parallel) → Compose digest

[vmanoharas]

Hi @aaronmahbuild,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

[aaronmah]

⚡ PR Update — v2 (updated files pushed)

Changes in this update:

• Removed updateIncident operation (returned 403 — requires Datadog Incident Management paid plan add-on)
• Operation count: 12 → 11 (all 11 pass on any Datadog plan)
• Auth fixed via paconn update — dual API key headers (DD-API-KEY + DD-APPLICATION-KEY) now injected correctly
• All 3 scenario flows revalidated against the updated 11-operation swagger
• Readme.md updated to reflect 11 operations

Updated Operations (11 total)

Operation	Type	Description
List Monitors	Action	Retrieves a list of all monitors with optional filtering by name, tags, or state
Get Monitor	Action	Retrieves the details of a specific monitor by its ID
Mute Monitor	Action	Mutes a monitor to suppress alert notifications
Unmute Monitor	Action	Unmutes a previously muted monitor to resume alerts
List Incidents	Action	Retrieves a list of incidents sorted by creation date
Get Incident	Action	Retrieves the full details of a specific incident by ID
Create Incident	Action	Declares a new incident with title, severity, and commander
Post Event	Action	Posts a custom event to the Datadog event stream
Get Host Totals	Action	Returns total number of active and up hosts
List SLOs	Action	Retrieves all Service Level Objective definitions
Create Downtime	Action	Schedules a downtime to suppress alert notifications

Test Results

• 11/11 operations tested successfully in PA environment
• swagger-cli validate passed (exit code 0)
• paconn validate passed
• 3 end-to-end scenario flows validated in Power Automate
• Screenshot validation ✅ 4/4 screenshots verified (green checkmarks present, no red indicators)

📝 Note to reviewer: The PR description above still references 12 operations. The files in this PR (swagger, Readme) are updated to reflect 11 operations. The updateIncident operation was removed because it requires a paid Incident Management add-on.

[vmanoharas]

Hi @aaronmahbuild,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip