Merge.dev and Turbot Pipes Integration

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

Connect Merge.dev and Turbot Pipes to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about Merge.dev and Turbot Pipes

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

  • Merge.dev

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

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

  • Turbot Pipes

    • Developer Tools
    • 68 searches
    • 79 actions

    Hosted SQL, dashboards and workflows for cloud data.[6]

How to connect Merge.dev to Turbot Pipes

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

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

WEXTL exposes actions and triggers for Merge.dev and Turbot Pipes 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.

Merge.dev triggersTurbot Pipes actions

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.

Turbot Pipes modules

  • Add a Workspace Connection Adds a connection inside a workspace under a Handle, built on a Plugin. Add Configuration for the settings and Parent ID to nest it in a folder.
  • Add an Organization Member Adds an existing user to an organization with the chosen Handle, and gives them a Role.
  • Add an Organization Workspace Member Grants a member of an organization access to one organization workspace with a chosen Role.
  • Attach a Schema Attaches a database schema to a workspace, linked to an Aggregator or to a Connection. A whole folder of connections can be pulled in through Connection Folder.
  • Create a Connection Adds a data connection under a Handle, built on a Plugin. Add Configuration for the plugin settings and Parent ID to nest it inside a folder.
  • Create a Datatank Provisions a datatank, a managed store for query results, under a Handle. Add a Description and set Desired State to control whether it runs.
  • Create a Datatank Table Defines a table with a Name and a Type. Tables either copy a source table or run a Source Query. Set Frequency to refresh them on a schedule.
  • Create a Flowpipe Input Answers a Flowpipe step that is waiting for input. Tie the answer to that step with Process ID, Step Execution ID, Step Type and Notifier Name.
  • Create a Mod Variable Setting Overrides one mod variable by giving a Setting for its Variable Name. The value can be a number, true, false or JSON.
  • Create a Notifier Makes an alert destination under a Name, with Notifies as a JSON array of targets. Use State to switch it on or off.
  • Create a Pipeline Defines a recurring job with a Title, the Pipeline to run, its Arguments and a Frequency. Use Tags to group it and Desired State to control whether it runs.
  • Create a Service Account Adds a non-human account to an organization. Add a Title and Description to explain what it is for.
  • Create a Service Account Token Issues an access token for a service account. Use Expiration to set a lifetime and Title or Description to label it.
  • Create a Snapshot Saves a dashboard result as a snapshot from Data in the format Turbot Pipes uses. Use Visibility to control who can open it and Tags or Title to label it.
  • Create a Trigger Starts a Pipeline on a Schedule and passes it Arguments each time. Add a Name, Title or State to describe it.
  • Create a User Token Issues an access token for a person. Use Expiration to give it a limited life and Title or Description to label it.
  • Create a Workspace Provisions a workspace under a unique Handle. Use Instance Type to size it, Database Volume Size (Bytes) for storage and Desired State to start or stop it.
  • Create an Aggregator Combines several connections of one Plugin into a single queryable schema under a Handle. Fill Connections with the members and Configuration for plugin settings.
  • Create an AI Key Stores an API Key for a Provider. The key itself never appears in the output, only its Last4 characters.
  • Create an Integration Creates an integration under a Handle with a given Type, using Configuration for the settings that type needs.
  • Create an Organization Creates an organization under a unique Handle. Use Display Name for a friendlier title, Plan ID to choose a plan and URL for a link.
  • Delete a Connection Removes a data connection from an owner account.
  • Delete a Conversation Removes a conversation with the AI helper from a workspace.
  • Delete a Datatank Removes a datatank, the managed store of query results.
  • Delete a Datatank Table Deletes one materialised table from the datatank that holds it.
  • Delete a Flowpipe Trigger Deletes a trigger that starts Flowpipe pipelines in Turbot Pipes.
  • Delete a Mod Variable Setting Deletes the override set on one mod Variable.
  • Delete a Notifier Deletes a notifier, the alert destination used by pipelines.
  • Delete a Pipeline Deletes a recurring pipeline from a workspace.
  • Delete a Service Account Removes a non-human account from an organization.
  • Delete a Service Account Token Revokes an access token that belongs to a service account.
  • Delete a Snapshot Deletes a dashboard result that was saved earlier.
  • Delete a User Token Revokes a personal access token of a user.
  • Delete a Workspace Deletes a workspace from an owner account.
  • Delete an Aggregator Deletes an aggregator that merges connections from a workspace.
  • Delete an AI Key Removes the stored key of one AI Provider from your account.
  • Delete an Integration Removes an integration from an owner account.
  • Delete an Organization Removes an organization from Turbot Pipes.
  • Detach a Schema Removes the link between a workspace and a database schema.
  • Get a Connection Loads one data connection with its Config source and Credential source.
  • Get a Conversation Retrieves one conversation with the AI helper, showing who created it and when.
  • Get a Datatank Pulls one datatank along with its Description and the time it was created.
  • Get a Datatank Table Reads one materialised table and shows the Datatank it lives in.
  • Get a Flowpipe Input Fetches an input that a waiting Flowpipe step asked for, by its Input ID.
  • Get a Flowpipe Pipeline Shows a Flowpipe pipeline with its Description and Last process.
  • Get a Flowpipe Trigger Reads one Flowpipe trigger with its Args and Default state.
  • Get a Mod Reads an installed mod, including its Alias, Branch and Constraint.
  • Get a Mod Variable Shows a mod variable with its Description, Enum and Format.
  • Get a Notifier Fetches the alert destination called a notifier, including who created it.
  • Get a Pipeline Pulls a recurring pipeline from a workspace, including its Args.

Explore alternative integrations

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

Automate Merge.dev and Turbot Pipes on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Merge.dev and Turbot Pipes.

How do I connect Merge.dev and Turbot Pipes?

Connect your Merge.dev and Turbot Pipes 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 Merge.dev and Turbot Pipes?

Example: when the "Watch Accounts" trigger in Merge.dev fires, WEXTL can "Add a Workspace Connection" in Turbot Pipes. Merge.dev has 15 triggers (including Watch Accounts, Watch Benefits, and Watch Contacts). Turbot Pipes has 147 actions (including Add a Workspace Connection, Add an Organization Member, and Add an Organization Workspace Member). Add filters and transforms between steps when you need them.[1]

Can Merge.dev trigger actions in Turbot Pipes, and Turbot Pipes in Merge.dev?

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 Merge.dev and Turbot Pipes?

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

Does Merge.dev integrate with Turbot Pipes in real time?

Yes. Trigger-based automations start the moment Merge.dev (or Turbot Pipes) 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 Merge.dev + Turbot Pipes 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 Merge.dev with Turbot Pipes?

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

References

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

  1. Merge.dev and Turbot Pipes integration source code, module specs and credentials implementation.
  2. Our Merge.dev and Turbot Pipes integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Merge.dev and Turbot Pipes, 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. Merge.dev integration information
  6. Turbot Pipes integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Merge.dev and Turbot Pipes, or get started