Connect Datadog to HubSpot

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

Adds a comment to a thread. See the documentation

Adds a contact to a specific static list. See the documentation

MCP and AI agents: **Prefer this action** when the user wants to **leave a note on a HubSpot contact** using a **contact ID** and note text. Exposes only hubspot, contactId, and noteBody (no engagement-type step, no reloadProps, no dynamic HubSpot schema fields). Do **not** use **Create Engagement** for this workflow. For every writable note property or non-contact associations, use **Create Note** instead. See the documentation

Archives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentation

Create a batch of companies in Hubspot. See the documentation

Create or update a batch of contacts by its ID or email. See the documentation

Update a batch of companies in Hubspot. See the documentation

Upsert a batch of companies in Hubspot. See the documentation

Clone a marketing email in HubSpot. See the documentation

Clone a site page in Hubspot. See the documentation

Create a new workflow. See the documentation

Create an association (link) between two CRM records. For example, associate a contact with a company, a deal with a contact, or a ticket with a company. Common association type IDs: contact→company (1), company→contact (2), deal→contact (3), contact→deal (4), deal→company (5), company→deal (6), ticket→contact (15), contact→ticket (16), ticket→company (26), company→ticket (25). See the documentation

Create associations between objects. See the documentation

Creates a new blog post in HubSpot. See the documentation

Create a WhatsApp, LinkedIn, or SMS message. See the documentation

Create a company in Hubspot. See the documentation

Create a contact workflow in Hubspot. See the documentation

Create a new CRM record (contact, company, deal, ticket, etc.). Pass property values as a JSON object in the properties parameter. Use **Search Properties** to discover available fields for the object type, **Get Properties** to find valid enum values (e.g. lifecyclestage, dealstage), and **List Pipelines and Stages** to find valid pipeline/stage IDs for deals and tickets. Use **List Owners** to find valid hubspot_owner_id values. See the documentation

Create a new custom object in Hubspot. See the documentation

Create a deal in Hubspot. See the documentation

Create a **task, meeting, email, call, or note** engagement with optional associations. Set **Engagement Type** and pass engagement fields in **Object Properties** (HubSpot property names, e.g. hs_note_body for notes). No reloadProps step and no **CONFIGURE_COMPONENT** requirement: association fields accept raw HubSpot IDs (use **Search CRM** or the Associations API to resolve associationType when needed). For **only** a note on a contact by ID, **Add Note to Contact** (hubspot-add-note-to-contact) is still simpler. See the documentation

Create a form in HubSpot. See the documentation

Create a landing page in Hubspot. See the documentation

Create a lead in Hubspot. See the documentation