STEP 1
Connect Apify and Merge.dev
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Apify and Merge.dev Integration
Build developer tools workflows between Apify and Merge.dev on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Merge.dev
Detailed info you need to know about Apify and Merge.dev integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to Merge.dev
Set up your Apify and Merge.dev integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and Merge.dev nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Apify and Merge.dev. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and Merge.dev work in WEXTL?
WEXTL exposes actions and triggers for Apify and Merge.dev that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Apify triggersMerge.dev actions
Apify modules
- Add Request to QueueCreates request to queue.
- Batch Add RequestsPerforms batch add requests.
- Build ActorBuilds actor.
- Charge Events in RunCharges events in run.
- Create ActorCreates actor.
- Create DatasetCreates dataset.
- Create Environment VariableCreates environment variable.
- Create Key-Value StoreCreates key-value store.
- Create Request QueueCreates request queue.
- Create ScheduleCreates schedule.
- Create TaskCreates task.
- Create VersionCreates version.
- Decode and Verify DataRetrieves decode and verify data.
- Delete ActorDeletes actor.
- Delete Build (Abort)Aborts build.
- Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
- Delete DatasetDeletes dataset.
- Delete Environment VariableDeletes environment variable.
- Delete Key-Value StoreDeletes key-value store.
- Delete RecordDeletes record.
- Delete RequestDeletes request.
- Delete Request QueueDeletes request queue.
- Delete Run (Abort)Aborts an Actor run (DELETE semantics).
- Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
- Delete ScheduleDeletes schedule.
- Delete TaskDeletes task.
- Delete VersionDeletes version.
- Delete WebhookDeletes webhook.
- Download Records (Batch Export)Retrieves download records (batch export).
- Encode and Sign DataEncodes and sign data.
- Get ActorReturns actor.
- Get Browser InfoReturns browser info.
- Get Browser Info (POST Variant)Returns browser info (post variant).
- Get BuildReturns build.
- Get Build (Cross-Actor)Returns build (cross-actor).
- Get Build LogReturns build log.
- Get Build Log (Cross-Actor)Returns build log (cross-actor).
- Get DatasetReturns dataset.
- Get Dataset ItemsReturns dataset items.
- Get Dataset StatisticsReturns dataset statistics.
- Get Default BuildReturns default build.
- Get Environment VariableReturns environment variable.
- Get Environment VariablesReturns environment variables.
- Get Key-Value StoreReturns key-value store.
- Get Last Task RunReturns last task run.
- Get List of ActorsReturns list of actors.
- Get List of BuildsReturns list of builds.
- Get List of DatasetsReturns list of datasets.
- Get List of Key-Value StoresReturns list of key-value stores.
- Get List of KeysReturns list of keys.
Merge.dev modules
- Create a ContactCreates a new contact object in Merge CRM.
- Create a LeadCreates a lead object with the given values in Merge CRM.
- Create a NoteCreates a note object with the given values in Merge CRM.
- Create a TaskCreates a Task object in Merge CRM with the given values. Supports optional fields such as owner, account, opportunity, due date, and status.
- Create a Timesheet EntryCreates a new timesheet entry for an employee in Merge HRIS.
- Create an AccountCreates a new account object in Merge CRM.
- Create an EngagementCreates an Engagement object in the CRM with the given values.
- Create an OpportunityCreates a new opportunity in Merge CRM with the specified values.
- Create Ignore ContactMarks a specific contact as ignored, nullifies properties, and prevents future synchronization. Requires a reason and message.
- Create Time OffCreates a time-off object with the given values.
- Create User Ignore EntryIgnores a specific row based on the model ID in the URL. These records will have their properties set to null, and will not be updated in future syncs. The "reason" and "message" fields in the request body will be stored for audit purposes.
- Get a Company by IDFetches a single company object from the HRIS system by its unique ID. Supports optional inclusion of remote data and shell records.
- Get a ContactReturns a paginated list of contacts from the CRM integration. Supports filtering, remote data options, and all query parameters available in Merge's CRM Contacts endpoint.
- Get a Contact by IDRetrieves a single CRM contact from Merge by its Contact ID. Optionally expands related objects and includes remote or shell data.
- Get a Dependent by IDRetrieves a specific Dependent object using its unique ID. Supports optional inclusion of remote, sensitive, or shell data.
- Get a Group by IDRetrieves a single group object using its unique ID.
- Get a Lead by IDRetrieves a lead object by its unique ID from Merge CRM.
- Get a Location by IDRetrieves a location object by its ID.
- Get a Note by IDReturns a note object with the given ID from Merge CRM.
- Get a Note's MetadataRetrieves metadata for a note's post endpoint from the Merge CRM.
- Get a Pay Group by IDReturns a single Pay Group object from Merge HRIS using its unique ID. Supports including remote or shell data.
- Get a Payroll Run by IDReturns a single payroll run object from Merge HRIS using its unique ID. Supports including remote or shell data.
- Get a Stage by IDReturns a stage object with the given ID from the CRM.
- Get a Task by IDReturns a task object with the given ID.
- Get a User by IDReturns a user object with the given ID in the CRM.
- Get Account MetadataReturns metadata for CRM account POSTs.
- Get Account Patch MetadataRetrieves metadata for updating an account, including supported writable fields and field types for the connected CRM. Use this to see which fields are allowed in PATCH /accounts/{id}.
- Get an AccountRetrieves a list of accounts from the connected CRM system.
- Get an Account by IDRetrieves a single account object by its unique account ID in the CRM.
- Get an Employee Benefit by IDFetches a single EmployerBenefit object by its ID.
- Get an Employee by IDReturns a single employee object using the provided employee ID.
- Get an Employee Payroll Run by IDRetrieves a single Employee Payroll Run object using its Merge Employee Payroll Run ID.
- Get an Engagement Type by IDRetrieves a single engagement type by its unique ID in the CRM.
- Get Bank InfoRetrieves a paginated list of bank info records for the connected account, supporting cursor-based automatic pagination.
- Get Bank Info by IDReturns a BankInfo object with the given ID.
- Get Benefit by IDRetrieves a single benefit record from Merge HRIS using its unique ID.
- Get BenefitsRetrieves a paginated list of benefit records from the integrated HRIS platform. The module supports filtering by employee, date ranges, remote ID, creation/modification windows, and includes options for returning deleted data, remote provider data, shell records, and expanded relations.
- Get CompaniesRetrieves a paginated list of company records from the Merge HRIS API, with optional filtering by creation dates, modification dates, deletion flags, remote data, and more.
- Get Contacts MetadataReturns metadata for CRM Contact POST requests in the Merge API.
- Get CRM Contact MetadataReturns metadata for CRM contact POSTs, including all fields required or optional when creating a new contact in the CRM.
- Get DependentsFetches a list of Dependent objects from the HRIS system, supporting filtering by employee, creation or modification dates, and optional inclusion of remote or sensitive data.
- Get Employee BenefitsRetrieves a paginated list of employer benefit objects with optional filtering.
- Get Employee Post MetaReturns metadata for creating employee records, including required fields, optional fields, and enum information.
- Get EmployeesRetrieves a list of Employee objects from BambooHR via the Merge HRIS API.
- Get EmploymentReturns a list of employment objects.
- Get Employment by IDReturns an employment object with the given ID.
- Get EngagementRetrieves a list of Engagement objects from Merge CRM with optional filters and automatic pagination.
- Get Engagement by IDRetrieves an engagement object using the provided unique ID.
- Get Engagement Metadata PostReturns metadata for engagement posts in the CRM.
- Get GroupsFetches a list of group objects from the connected HRIS system. Supports filtering by creation/modification date, type, team usage, and remote ID.
Frequently asked questions
Common questions about connecting Apify and Merge.dev.
Connect your Apify 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]
Example: when Apify's "Watch Run Aborted" fires, WEXTL can "Create a Contact" in Merge.dev. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); 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]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Apify-to-Merge.dev automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Apify (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]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Apify + Merge.dev automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Apify and Merge.dev integration.
- Apify and Merge.dev integration source code, module specs and credentials implementation.
- Our Apify and Merge.dev integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Merge.dev — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Apify integration information
- Merge.dev integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library