Connect Make to Rig

    Sync your Make organisations, teams and scenarios into Rig, with each scenario's execution logs, notes and blueprint. The blueprint holds every module's field mappings, so you can trace which scenarios read or write a given field. Make connects with an API token and your regional Make URL.

    Before you start

    • You need a Make user who can see the organisations and teams you want to cover. The token reads what its owner can read.
    • Know your Make zone, which is part of the address you sign in at, such as eu1.make.com or us1.make.com.

    Step 1: Create a Make API token

    1. Sign in to Make and click your avatar at the bottom left.
    2. Click Profile and open the API tab.
    3. Click Add token.
    4. Enter a Label such as Rig.
    5. Under Scopes, select organizations:read, teams:read and scenarios:read. Rig only reads, so it needs nothing else.
    6. Click Save and copy the token. Make hides it once you leave the page.

    One token per zone
    If you use more than one Make zone, each zone needs its own token. Connect each zone as its own source.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Make, open the card and click Connect.
    3. API token: paste the token you created.
    4. Make instance URL: enter your zone address, for example https://eu1.make.com or https://us1.make.com.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Make lands in its own make schema in your warehouse:

    • Organizations: the Make organisations the token can see.
    • Teams: the teams in each organisation.
    • Scenarios: every scenario, with its team.
    • Scenario logs: each scenario's execution logs.
    • Scenario notes: the notes attached to scenarios.
    • Scenario blueprints: each scenario's blueprint, including the field mappings of every module.

    Good to know

    • Make's API accepts a token only for the zone it was created in, and Rig sends it only to make.com. Entering a different host is not possible.
    • Rig paces its requests well below Make's per-minute API limit, which was around 60 requests a minute on the Core plan, so a large account takes longer on a first sync.
    • Blueprints are the largest table. They are what lets you search for a field name across every module of every scenario.
    • To disconnect Make, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Trace which scenarios read or write a field
    • Inventory your automations by team
    • Review scenario run history

    More ideas for using Make

    Make documentation

    Was this guide helpful?