Datadog and Merge.dev Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Datadog and Merge.dev matched by integrating their events and actions. When developer tools events happen in Datadog, update the Merge.dev automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Datadog and Merge.dev

Detailed info you need to know about Datadog and Merge.dev integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Datadog

    • Developer Tools
    • 6 triggers
    • 63 searches
    • 70 actions

    Monitoring and security platform for cloud applications.[5]

  • Merge.dev

    • Developer Tools
    • 15 triggers
    • 62 searches
    • 18 actions

    Unified API platform that connects HRIS, ATS, and CRM systems through a single integration.[6]

How to connect Datadog to Merge.dev

Set up your Datadog and Merge.dev integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Datadog and Merge.dev work in WEXTL?

WEXTL exposes actions and triggers for Datadog and Merge.dev that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Datadog triggersMerge.dev actions

Datadog modules

  • Acknowledge an On-Call Page Marks a Datadog On-Call page as acknowledged by the responder.
  • Add a Case Comment Adds a written Comment to a Datadog case. Output has an ID, Author and Created At for the new comment.
  • Add a Team Member Gives a user membership of a Datadog team. Set Role to Admin to let them manage it, or leave it blank for a regular member.
  • Add Dashboards to a List Puts one or more dashboards into a manual Dashboard List, each given by its Dashboard and Type.
  • Add Host Tags Attaches Tags to a host. Source of user marks tags added by hand, and a blank Source covers every source.
  • Aggregate Logs Works out a count, unique count, average or sum over matching log events. Use Group By to split the result by facet, Metric to pick the attribute to compute, and Indexes to search only some log indexes.
  • Archive a Case Archives a Datadog case, which sets its Archived At time. The updated case record is returned.
  • Assign a Case Gives a Datadog case to an Assignee, the user who owns the case.
  • Cancel a Downtime Cancels a downtime, which is a muting window for monitors in Datadog.
  • Cancel a Workflow Run Cancels a Datadog workflow run that is still running.
  • Create a Case Opens a case under a case project, giving it a Title and Type. Use Priority to rank it, Description to explain it and Assignee to give it an owner.
  • Create a Case Project Creates a case project named by Name, with a short Key code that case IDs start with.
  • Create a Dashboard Builds a dashboard from a Title, a Layout Type of Ordered or Free, and a list of Widgets. Add Template Variables so viewers can filter, and turn on Read Only to limit edits to the author and admins.
  • Create a Dashboard List Creates a manual list under a Name, ready to collect dashboards. Output includes the Dashboard Count and ID.
  • Create a Downtime Plans a muting window for a Scope, either one time or recurring through Schedule. Use Mute First Recovery to silence the first recovery notification of a monitor that was already alerting.
  • Create a Global Variable Stores a Synthetics global variable from a Name, Description and Value. Turn on Secure to hide the value once it is saved.
  • Create a Monitor Creates a monitor of a given Type that evaluates a Query. Use Critical Threshold, Warning Threshold and OK Threshold for alert levels, and Message with @handles to choose who is notified.
  • Create a Team Creates a team from a Name and a unique Handle used in @mentions. Add a Description, and use Members to add users to it.
  • Create a User Adds a user from an Email address. Use Name and Title to fill in the profile.
  • Create an API Test Sets up a Synthetics API test with a Name, a Subtype of HTTP, SSL, TCP or DNS, a Frequency and the Locations it runs from. Add Assertions to define what must pass, and a Message for failure notifications.
  • Create an Event Sends an event into the Datadog event stream under a Title and Category. Use Aggregation Key to group related events and Timestamp to set when it happened.
  • Create an Incident Declares an incident from a Title and a Customer Impacted answer. Use Severity to rank it, State to mark where it stands, and Commander to name the lead.
  • Create an Incident Impact Logs a customer impact for an incident, giving a Description and a Start time. Leave End blank while the impact is still going.
  • Create an Incident Todo Attaches a task to an incident, written as its Content. Use Assignees to name who owns it and Due Date to set a deadline.
  • Create an On-Call Page Raises an On-Call page with a Title and an Urgency of Low or High. Use Target Type to page by team, team handle or user, and Description to add detail for the person who is paged.
  • Create an SLO Creates a service level objective from a Name, a Type of Metric or Monitor, and Thresholds. A metric SLO compares two metric queries, and a monitor SLO is based on monitors.
  • Create an SLO Correction Excludes a period from an SLO calculation. Give a Category as the reason and use Time Zone to say which zone the period uses.
  • Delete a Dashboard Deletes the chosen dashboard from your Datadog account.
  • Delete a Dashboard List Removes a manual list of dashboards from Datadog.
  • Delete a Monitor Removes a monitor. Turn on Force Delete to remove it even when an SLO or composite monitor depends on it.
  • Delete a Notebook Deletes a single notebook document stored in Datadog.
  • Delete a Team Deletes a team from your Datadog organization.
  • Delete an Incident Deletes an incident record from Datadog.
  • Delete an SLO Removes a service level objective. Turn on Force Delete to remove it even when a dashboard or monitor refers to it.
  • Delete an SLO Correction Removes one correction that excluded a period from an SLO.
  • Delete Host Tags Clears the tags attached to a host. Use Source to clear only the tags that came from one source.
  • Delete Tests Deletes one or more Synthetics tests in a single call. Turn on Force Delete Dependencies to delete them even when other resources depend on them.
  • Disable a User Disables a user account in your Datadog organization. Turning Disabled off on that user enables the account again.
  • Escalate an On-Call Page Moves an On-Call page up to the next level of its escalation policy.
  • Get a Case Fetches one Datadog case with its Attributes, Description and Created At.
  • Get a Case Project Reads a case project with its Key, Name and Settings.
  • Get a Dashboard Loads a dashboard, including its Author Handle, Description and Default Timeframe.
  • Get a Dashboard List Looks up a manual dashboard list and shows its Name, Author and Dashboard Count.
  • Get a Downtime Pulls up a downtime with its Message, Display Timezone and Monitor Identifier.
  • Get a Global Variable Reads a Synthetics global variable and its Restricted Roles.
  • Get a Monitor Retrieves a monitor with its Creator, Draft Status and Matching Downtimes. Set Include Downtimes to Yes to add the active downtimes of the monitor.
  • Get a Notebook Gets a notebook along with its Author, Cells and Modified.
  • Get a Synthetics Test Looks up a Synthetics test and its Config, Locations and Monitor ID.
  • Get a Team Retrieves a team with its Handle, Description and Created At.
  • Get a User Loads a user together with their Email, Handle and Disabled.

Merge.dev modules

  • Create a Contact Adds a person to the CRM, starting from their First Name. Attach a Last Name and an Account, plus Phone Numbers or Email Addresses, each with a type such as Mobile or Work.
  • Create a Lead Adds a lead to the CRM with a Lead Source, Title and Company, plus First Name and Last Name. Use Converted Contact and Converted Account to link a lead that already became a contact and account.
  • Create a Note Writes note Content into the CRM and attaches it to an Account ID, a Contact ID or an Opportunity ID, one at a time. Give an Owner ID to assign the note.
  • Create a Task Opens a CRM task with a Subject and Content, an Owner, a Due Date and a Status. Link it to an Account, an Opportunity or a Contact.
  • Create a Time Off Request Records a time off request for an Employee, with an Approver, a Start Time and End Time. Use Time-Off Units to count the Amount in hours or days, and add an Employee Note for the reason.
  • Create a Timesheet Entry Books hours against an Employee, with Hours Worked and a Start Time in ISO 8601.
  • Create an Account Adds a CRM account with an Account Name and a Number of Employees. Assign an Owner ID, and give the account one or more postal addresses through Addresses.
  • Create an Engagement Logs an engagement in the CRM against an Owner, an Account or a Subject, with at least one of the three supplied. It can also carry an Engagement Type and related Contacts.
  • Create an Opportunity Adds an opportunity under an Opportunity Name, with an Amount and a Status of OPEN, WON or LOST. Tie it to an Account ID, an Owner ID and a Stage ID. Output includes the new Opportunity ID.
  • Get a Bank Info Record by ID Reads one bank account saved for an employee, with its Bank name, Account type, Account number and Routing number.
  • Get a Benefit by ID Loads one benefit with its Provider name, Employee contribution and Company contribution, plus Start date and End date.
  • Get a Company by ID Fetches one company from the HRIS with its Legal name, Display name and Eins.
  • Get a Contact by ID Pulls a CRM contact by ID with their First name, Last name, Email addresses and Phone Numbers. Use Expand with a value like account,owner to return those relations in full.
  • Get a Dependent by ID Reads a dependent of an employee: Relationship, Date of birth, Gender and Is student. Turn on Include Sensitive Fields to add values such as social security numbers.
  • Get a Group by ID Reads a group, showing its Parent group, Type and whether Is commonly used as team is set. Use Show Enum Origins to return enum values as the provider names them.
  • Get a Lead by ID Pulls one CRM lead, including its Company and Lead source.
  • Get a Location by ID Reads one location with its Street 1, City, State, Zip code, Country and Location type.
  • Get a Note by ID Loads a note with its Content and the Contact, Account and Opportunity it is linked to.
  • Get a Pay Group by ID Reads one pay group and returns its Pay group name from the HRIS.
  • Get a Payroll Run by ID Reads one payroll run with its Run state, Run type, Start date, End date and Check date.
  • Get a Stage by ID Reads one pipeline stage from the CRM and returns its Name.
  • Get a Task by ID Reads a task, listing the Subject, Due date, Completed date and Status.
  • Get a Time Off Balance by ID Reads a time off balance with the Balance, Used and Policy type for one employee.
  • Get a Time Off Request by ID Loads one time off request with its Employee, Approver, Status, Request type and Amount. Use Expand Relations with a value like employee,approver to return those people in full.
  • Get a User by ID Reads one CRM user, with a Name, an Email and an Is active flag.
  • Get Account Metadata Describes the payload of an account create call in the CRM, giving a Request schema and a Status.
  • Get Account Patch Metadata Describes what updating one existing account will accept, as a Request schema.
  • Get Accounts Lists CRM accounts, showing Name, Industry, Website and Number of employees. Search by Name or Owner ID.
  • Get an Account by ID Pulls one CRM account with its Name, Industry, Website and Number of employees.
  • Get an Employee by ID Reads one employee with an Employee number, Preferred name, Username and Work email. Turn on Include Sensitive Fields for sensitive values, or use Show Enum Origins to get the provider enum values.
  • Get an Employee Payroll Run by ID Reads what one employee received in a payroll run: Gross pay, Net pay, Earnings, Deductions and Taxes.
  • Get an Employer Benefit by ID Reads a benefit offered by the employer, including its Benefit plan type, Name and Deduction code.
  • Get an Employment by ID Reads one employment record, showing the Job title, Pay rate, Pay frequency, Pay currency and Effective date. Use Show Enum Origins to get the original third-party values of enum fields.
  • Get an Engagement by ID Returns an engagement from the CRM, showing the Direction, Engagement type and Start time. Turn on Include Remote Fields to add fields not mapped to the common model.
  • Get an Engagement Type by ID Fetches one engagement type, giving its Name and Activity type.
  • Get an Opportunity by ID Reads an opportunity from the CRM, covering its Amount, Stage, Status and Close date.
  • Get Bank Info Records Lists saved bank accounts with Bank name, Account type, Routing number and Employee. Restrict by Employee ID, Account Type (SAVINGS or CHECKING) or Bank Name, and sort with Order By.
  • Get Benefits Lists benefits with the Provider name, Benefit plan type, Employee contribution and Company contribution of each. Use Employee ID to return the benefits of one employee.
  • Get Companies Lists companies with their Legal name, Display name and Eins. Turn on Include Deleted Data to also return companies deleted in the third-party platform.
  • Get Contacts Lists CRM contacts with First name, Last name, Account and Owner. Search by Account ID, Email Addresses or Phone Numbers.
  • Get Contacts Metadata Lists what a create call for a CRM contact will accept, in a Request schema alongside a Status and Has conditional params.
  • Get CRM Contact Metadata Shows the shape of a valid new CRM contact as a Request schema, with Has required linked account params.
  • Get Dependents Lists dependents with Relationship, Date of birth and Is student. Use Employee ID to see the dependents of one employee.
  • Get Employee Creation Metadata Fetches the fields a new HRIS employee may carry, as a Request schema with Has conditional params.
  • Get Employees Lists employees with filters such as Job Title, Employment Status, Manager ID, Team ID or Work Email. Each has an Employee number, names and a Work email.
  • Get Employer Benefits Lists the benefits an employer offers, each with a Benefit plan type, Name and Deduction code.
  • Get Employments Lists employment records with Job title, Pay rate, Pay period and Employment type. Use Order By to sort by effective date, and Employee to see one person.
  • Get Engagement Creation Metadata Pulls the Request schema behind engagement creation, together with Remote field classes from the linked CRM.
  • Get Engagements Lists CRM engagements with Subject, Direction and Engagement type, plus when each began and ended. Narrow by when they began with Started After and Started Before.
  • Get Groups Lists groups from the HRIS, returning a Name, a Type, a Parent group and an Is commonly used as team flag per group. Narrow them through Group Types or Group Names.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Datadog and Merge.dev integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Datadog and Merge.dev on WEXTL®

Claim your 3-day trial to build Datadog with Merge.dev integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Datadog and Merge.dev.

How do I connect Datadog and Merge.dev?

Connect your Datadog and Merge.dev accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Datadog and Merge.dev?

Example: when the "Watch Audit Logs" trigger in Datadog fires, WEXTL can "Create a Contact" in Merge.dev. Datadog has 6 triggers (including Watch Audit Logs, Watch Cases, and Watch Events). Merge.dev has 80 actions (including Create a Contact, Create a Lead, and Create a Note). Add filters and transforms between steps when you need them.[1]

Can Datadog trigger actions in Merge.dev, and Merge.dev in Datadog?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Datadog and Merge.dev?

No. Datadog-to-Merge.dev automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Datadog integrate with Merge.dev in real time?

Yes. Trigger-based automations start the moment Datadog (or Merge.dev) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Datadog + Merge.dev integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Datadog with Merge.dev?

You can build your Datadog + Merge.dev automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Datadog and Merge.dev integration.

  1. Datadog and Merge.dev integration source code, module specs and credentials implementation.
  2. Our Datadog and Merge.dev integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Datadog and Merge.dev, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Datadog integration information
  6. Merge.dev integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Datadog and Merge.dev integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Datadog and Merge.dev, or get started