api API Documentation

Batch Migration API

Automatically migrate all your Pipedrive V1 scenarios to V2 using a Make.com template scenario. Set it up once, run it, and every scenario gets migrated in seconds.

rocket_launch Quick Start

1

Download & Import the Template

Download the Make.com scenario blueprint below, then import it into your Make.com account via Scenarios → Create a new scenario → Import Blueprint.

download Download Scenario Template
2

Run the Setup Route (Bottom Row)

The template has two routes. Start with the bottom route — connect your Make.com account, then run it to automatically discover your Team ID and Pipedrive Connection ID. See details below ↓

3

Configure the Migration Route (Top Row)

In the top route, fill in 4 placeholders — your migration token, connection ID, team ID, and folder ID. See details below ↓

4

Run the Migration

Click "Run once" on the top route. The scenario will automatically scan your scenarios, filter for Pipedrive V1, migrate each one, and create migrated V2 copies in your chosen folder.

edit_note What You Need to Edit

After importing the template and running the setup route, configure the following 4 placeholders in the migration route:

link

Make Connection

Make Modules

Open the Make modules in the scenario (List Scenarios, Get Blueprint, and Create Scenario). Connect your Make.com account and select your team from the dropdown.

// In each Make module:
1. Click the module → select your Make connection
2. Choose your Team from the dropdown
key

Migration Token

required

The access token provided to you by Innovaty. This authenticates your requests and tracks your migration credits. Each successful migration deducts 1 credit.

// In the "Migrate-v2" module → replace <key>
"token": "abc123-your-token-here"
cable

Pipedrive Connection ID

required

Your Pipedrive OAuth connection ID. Get this from the setup route output (Step 2 of the List Connections module), or find it by opening any Pipedrive module in Make.com.

// In the "Migrate-v2" module → replace <connection_id>
"connection_id": 4683394
groups

Team ID

required

Your Make.com team ID. Get this from the setup route output (Step 1 of the List Teams module).

// In the "Scenario Json" module → replace <team id>
"teamId": 123456
folder

Folder ID

required

The destination folder where migrated scenarios will be created. Find it in your Make.com URL when viewing a folder (the number after /folder/).

// In the "Scenario Json" module → replace <folder id>
"folderId": 789012
database

Required: Create the Data Structure

The Scenario JSON module uses a data structure to build the API payload. Since data structures are account-specific, you need to create one in your Make.com account:

  1. Open the Scenario JSON module (Create JSON)
  2. Click "Add" next to the Data Structure dropdown
  3. Name it anything (e.g. scenario_payload)
  4. Add 4 text fields with these exact names:
scheduling → type: Text
blueprint  → type: Text
teamId    → type: Text
folderId  → type: Text

After saving, the module will show input fields for each — map scheduling and blueprint from the Migrate response, and enter your team ID and folder ID manually.

warning

Important: Webhook Triggers

Scenarios with webhook triggers will have their webhook bindings removed during migration (they can't be reused). After migration, you'll need to create a new webhook in each migrated scenario and update the trigger module.

search Check V1 Endpoint

POST https://www.innovaty.co/api/check-v1

Lightweight check to determine if a blueprint contains Pipedrive V1 modules. Use this as a pre-filter before calling the migration endpoint to avoid unnecessary processing.

Request Body

{
  "blueprint": { // The full scenario blueprint JSON
    "flow": [...],
    "name": "My Scenario"
  }
}

Response

{
  "has_v1": true,
  "v1_modules": [
    {
      "id": 4,
      "module": "pipedrive:searchPersons",
      "type": "generic_replacement"
    }
  ]
}

sync_alt Batch Migrate Endpoint

POST https://www.innovaty.co/api/batch-migrate

Migrates a single Pipedrive V1 blueprint to V2. Returns the migrated blueprint as JSON, ready to be uploaded as a new scenario. Deducts 1 credit per successful migration.

Parameters

token string
required

Your migration access token

blueprint object
required

The full scenario blueprint JSON object

connection_id integer
required

Your Pipedrive OAuth connection ID in Make.com

activity_mode string
optional

"keep_v1" (default) or "migrate_v2". Controls whether Activity modules are kept as V1 or upgraded.

Request Body

{
  "token": "your-token-here",
  "blueprint": { // Full blueprint from Make.com API
    "flow": [...],
    "name": "My CRM Workflow" // used for output name
  },
  "connection_id": 4683394,
  "activity_mode": "keep_v1"
}

Success Response

{
  "migrated_blueprint": "{ ... }", // Stringified JSON — ready for Create Scenario
  "migrated_name": "migrated_v2 My CRM Workflow",
  "credits_remaining": 4,
  "warnings": {
    "trigger_warnings": ["Webhook trigger found — create a new webhook after migration"],
    "field_warnings": ["Field ID '12345' may need manual remapping"],
    "custom_field_warnings": []
  }
}

Skipped Response (No V1 found)

{
  "status": "skipped",
  "reason": "No Pipedrive v1 modules found"
}

tune Setup Route (Bottom Row)

Run this route first to discover your Team ID and Pipedrive Connection ID. These values are needed in the migration route above.

groups

List Teams

Make Module Step 1

Fetches all teams in your Make.com organization. Note the Team ID from the output — you'll paste it into the Scenario JSON module.

arrow_downward passes team to →
cable

List Connections

Make Module Step 2

Lists all connections for your team. Look for your Pipedrive OAuth connection and note its Connection ID (the numeric ID).

arrow_downward filters connections →
bookmark

Set Variable — Pipedrive Connection ID

Utility Step 3

Automatically filters for "Pipedrive OAuth" connections and stores the result. Verify the correct connection was selected.

schema Migration Flow (Top Row)

After completing the setup route, this is the main migration flow. It scans, migrates, and creates new V2 scenarios automatically.

view_list

List Scenarios

Make Module

Fetches all scenarios from your team. Set the Limit to control batching — start with 1 to test, then increase.

filter_alt routes each scenario →
description

Get a Scenario Blueprint

Make Module

Fetches the full blueprint JSON and scheduling data for each scenario.

filter_alt passes blueprint →
language

Check V1 Modules

HTTP → Innovaty API

POST https://www.innovaty.co/api/check-v1
Sends the blueprint to our API to detect Pipedrive V1 modules. No auth needed.

filter_alt only if has_v1 == true →
language

Migrate Blueprint

HTTP → Innovaty API

POST https://www.innovaty.co/api/batch-migrate
Sends the V1 blueprint with your token and connection ID. Returns a fully migrated V2 blueprint. Uses 1 credit.

arrow_downward builds scenario payload →
data_object

Scenario JSON

JSON

Constructs the final JSON payload for creating the V2 scenario, including the migrated blueprint, scheduling, team ID, and folder ID.

arrow_downward creates scenario →
add_circle

Create V2 Scenario

Make API Call

Creates the migrated V2 scenario in your Make.com account using the Make API. The new scenario is created as inactive — review it before activating.

format_list_numbered Response Codes

Code Meaning
200 Success — migration completed or check returned results
400 Missing required field (blueprint, connection_id)
401 Missing or invalid token
402 Trial limit reached — no credits remaining
403 Invalid token
500 Internal server error

help Frequently Asked Questions

Will my original scenarios be modified?

No. The original scenarios are never touched. The migration creates brand new copies in the "Pipedrive Migration" folder. You can review and test them before switching over.

What happens if a migration fails?

No credit is deducted for failed migrations. The template scenario will log the error and continue with the next scenario. You can check the execution history in Make.com to see details.

Do I need to create new webhooks?

Yes, for scenarios that use webhook triggers. Webhook bindings can't be shared between scenarios, so you'll need to create new webhooks in the migrated copies. The migration output includes warnings when this applies.

What does "activity_mode" do?

"keep_v1" (default) — keeps Create/Update Activity modules as V1, since V2 activity modules have known timezone issues.
"migrate_v2" — upgrades Activity modules to V2 as well. Only use this if you're prepared to handle potential time offset issues.

How many scenarios can I migrate?

Each migration token comes with a set number of credits. Each successful migration uses 1 credit. Contact us for unlimited account migration access.