Connect Stripe to Datadog

Cancel a PaymentIntent. See the documentation.

Cancel a pending payout or reverse a paid payout. See the documentation here and here

Cancel a subscription. See the documentation

Capture the funds of an existing uncaptured payment intent. See the documentation.

Confirm that your customer intends to pay with current or provided payment method. See the documentation.

Create a customer. See the documentation.

Create a payment intent. See the documentation.

Create a payout. See the documentation.

Create a refund. See the documentation.

With metered billing, you charge your customers based on their consumption of your service during the billing cycle, instead of explicitly setting quantities. Use this action to create a usage record for metered billing. See the docs for more information

Creates a billing meter. See the documentation.

Create an invoice. See the documentation.

Add a line item to an invoice. See the documentation.

Creates a new price for an existing product. The price can be recurring or one-time. See the documentation

Creates a new product object in Stripe. See the documentation.

Create a subscription. See the documentation.

Delete a customer. See the documentation.

Delete a line item from an invoice. See the documentation.

Delete a draft invoice, or void a non-draft or subscription invoice. See the documentation.

Finalize a draft invoice. See the documentation.

List all balance transactions. By default returns an array of transaction objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate. See the documentation.

Find or list customers. By default returns an array of customer objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate. See the documentation.

Find or list invoices. By default returns an array of invoice objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate. See the documentation.

Retrieves a list of payment intents that were previously created. By default returns an array of payment intent objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate. See the documentation.

Detect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g. datadoghq.com) which must be passed as the region parameter to **Search Logs**, **Search Monitors**, **Get Metric Data**, and all other Datadog tools. See the docs

Detect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions. See the docs

Query time-series metric data for analyzing trends and system performance. Query syntax: avg:system.cpu.user{*}, sum:requests.count{env:prod} by {host}, max:system.mem.used{service:web}. Both from and to are POSIX timestamps in seconds. Use **Search Metrics** first to discover available metric names. Use **Search Hosts** to find valid host tags for scoping. After finding anomalies, use **Search Logs** to investigate related entries. See the docs

Get a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr). See the docs

Post custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via **Get Metric Data**. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g. {"1640995200": 1.0}. Use **Search Metrics** to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series. See the docs

List and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL: https://app.{region}/dashboard/{id} where region comes from **Get Account Info**. Use alongside **Search Services** to find dashboards related to a specific service. See the docs

Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use **Search Monitors** first, then search events for the relevant time range. Follow up with **Search Logs** for deeper investigation. See the docs

Search monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort by cpu, iowait, load, status, or apps. Host names from results can scope queries in **Get Metric Data** (e.g. avg:system.cpu.user{host:web-01}), filter logs in **Search Logs** (host:web-01), or filter metrics in **Search Metrics**. Max 1000 results. See the docs

Search Datadog incidents by state, severity, and metadata. Query syntax: state:active, state:resolved, severity:SEV-1. After finding an incident, investigate with: **Search Logs** for the incident time window, **Get Metric Data** for relevant metrics, **Search Events** for related monitor alerts, and **Search Services** for ownership info. See the docs

Search Datadog logs matching a query with support for facets and time ranges. Uses log search syntax: service:web-app status:error, @http.status_code:>=400, boolean operators (AND, OR, NOT), and wildcards. Set from to now-1h for recent logs. Use **Search Metrics** to discover metric names or **Search Hosts** to find host names for filtering. To investigate an incident, use **Search Incidents** first, then search logs for that time window and service. See the docs

Discovery tool: list available Datadog metric names, optionally filtered by host. Returns metric name strings (e.g. system.cpu.user, aws.ec2.cpuutilization) for use in **Get Metric Data** queries with the syntax aggregation:metric.name{tags}. Use **Search Hosts** to find valid host names for the host filter. See the docs

Search Datadog monitors (alerting rules) including status, thresholds, and conditions. Query syntax: tag:env:production, type:metric, status:Alert. Tags filter: comma-separated (e.g. env:prod,team:backend). After finding a monitor, use **Search Events** to see recent state changes, or **Get Metric Data** to query the underlying metric it tracks. Returns monitor ID, name, type, query, status, and tags. See the docs

List services from Datadog's Service Catalog with ownership, metadata, and team info. Use to discover service names for filtering in **Search Logs** (service:my-app) or finding monitors via **Search Monitors** (tag:service:my-app). Returns service definitions including links, docs, and on-call. See the docs