Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Datadog

Cloud monitoring and analytics platform

CategoryDeveloper Tools
Authenticationcustom
Version0.2.1
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Datadog with Flows360

Cloud monitoring and analytics platform

Use the Datadog connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 3 actions and no declared triggers.

Available actions

  • Send Multiple logs
  • Send One log
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Datadog
  • Package: @activepieces/piece-datadog@0.2.1
  • Exact artifact digest: sha256:50e3e39eb8cad70ae4fc3a063f6297a547b3ccf27d0459926ffc0dacc9d87ec0
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Multiple logs (sendMultipleLogs), Send your logs to your Datadog platform over HTTP. Classification: read.
  • Send One log (sendOneLog), Send one log to your Datadog platform over HTTP. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Datadog API key Required · protected credential
  • Datadog App key (required for some endpoints) Optional · protected credential
  • Site Required

Supported objects

ObjectReadWriteNotes
Send Multiple logs Yes No Send your logs to your Datadog platform over HTTP.
Send One log Yes No Send one log to your Datadog platform over HTTP.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Send Multiple logs · Read

Send your logs to your Datadog platform over HTTP.

send_multiple_logs · Risk: low · Retry: safe

Inputs

  • body · object · Required, Logs to send to Datadog, must contain a `logs` key with an array of objects. Documentation: https://docs.datadoghq.com/api/latest/logs/#send-logs
Send One log · Read

Send one log to your Datadog platform over HTTP.

send_one_log · Risk: low · Retry: safe

Inputs

  • message · string · Required, The message to send to Datadog
  • ddsource · string · Optional, The DD source to send to Datadog
  • ddtags · string · Optional, The DD tags to send to Datadog, comma separated
  • hostname · string · Optional, The hostname to send to Datadog
  • service · string · Optional, The service to send to Datadog
  • additionalProperties · object · Optional, Additional properties to send to Datadog, in key-value pairs like status, level, etc.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Datadog connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Datadog API key (apiKey), required; stored as a sensitive connection value.
  • Datadog App key (required for some endpoints) (appKey), optional; stored as a sensitive connection value.
  • Site (site), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-datadog@0.2.1; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Datadog connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-datadog@0.2.1 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com