Resources · Make integration

Twin Web Agent Make integrationAutomate Twin Web Agent with Make.

Can another app hand work to Twin Web Agent without you in the loop? The Twin Web Agent Make integration gives you 2 action modules and no trigger. This page is for ops people who already use the agent: connect it, then build a first scenario that starts a browsing task.

Try the Twin Web Agent integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Twin Web Agent Make integration do?

It lets a Make scenario, the automation you build in Make as a chain of modules, send work to Twin Web Agent. You get 2 modules, both actions: one starts a browsing task, the other calls any endpoint of the Twin Web Agent API. Nothing in Twin Web Agent can start the scenario, so another app or a schedule opens the flow.

A lead that gets researched on arrival. A sales team receives a new form entry in another app; that app starts the scenario, and Start a Browsing Task passes the request to the agent. Each module in the chain is one brick, and each item moving between bricks is called a bundle.

A support ticket that gets context. When a ticket lands in a help desk connected to Make, the scenario can hand the agent a browsing task with details mapped from that ticket, so nobody copies text by hand.

Anything the listed modules skip. Make an API Call reuses your connection to reach any endpoint of the Twin Web Agent API, which is the fallback when the 2 modules are not enough.

Be clear on the limit: the official doc says it cannot yet provide complete documentation for Twin Web Agent, because too little public information exists. Fields, formats and returned data are not described, so test every step with Run once. If you want a view of the platform before you build, read the Make review; if you are weighing tools, the n8n vs Make comparison lays out both, and the same app often has an n8n node too. Stuck on an error? See Make troubleshooting.

Connect

How do you connect Twin Web Agent to Make?

  1. 01

    Add a Twin Web Agent module

    In your scenario, click the +, search for Twin Web Agent and pick a module. Then click Create a connection. A connection is your Twin Web Agent account linked to Make once, and every module of the app reuses it.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If two teams or two accounts use the agent, a clear name tells you at a glance which account a module is working with.

  3. 03

    Authorize and save

    Depending on what the app asks for, either approve Make on the Twin Web Agent page or paste the key the app gives you. Then click Save, and the module can use the account.

First scenario

Your first scenario with Twin Web Agent

GoalWhen a new request arrives in another app, Make starts a browsing task in Twin Web Agent.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Twin Web Agent has no trigger, pick the app where requests appear, like your form tool.

  2. 02

    Add Start a Browsing Task

    Click the + on the right of that first module, search for Twin Web Agent and choose Start a Browsing Task. Create the connection if this is your first time.

  3. 03

    Map the request

    Fill the module fields with data from the previous module: click a field, then pick the value it received. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module's bubble to read the bundles it received and confirm the agent got what you meant to send.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default for a new scenario, then turn the scenario on. From now on each new request reaches the agent without you.

Modules

What can Twin Web Agent do in Make?

Twin Web Agent gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Twin Web Agent1

Make an API Call

ActionIn the docs only

This module lets you reach any endpoint of the Twin Web Agent API from your scenario, reusing the connection you already created, so you are never limited to the one ready-made action.

When to use it
you need something from the agent that Start a Browsing Task does not cover, and the Twin Web Agent API documents that endpoint.
Watch out
the Make doc for this app is incomplete, so use this only for an endpoint Twin Web Agent itself documents, and test the call with Run once.
Twin Web Agent2

Start a Browsing Task

ActionIn the docs only

Here is the action most readers come for: judging by its name, it hands the agent a browsing task from inside your scenario, fed by data from earlier modules instead of someone typing the request.

When to use it
a new entry in another app, such as a form reply or a ticket, should turn into work for the agent right away.
Watch out
the doc describes neither its fields nor what it sends back, so check the output bundle after Run once before chaining another module.
Need help

Need help automating Twin Web Agent with Make?

A person reads every message.

FAQ

Twin Web Agent and Make: common questions

01Is the Twin Web Agent Make integration free?
Yes, Twin Web Agent is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each operation, meaning one module running on one bundle, counts against your plan. Paid plans lower the interval to 1 minute and allow 40 minutes of execution. Any cost on the Twin Web Agent side is separate and not covered here.
02What is needed to connect Twin Web Agent to Make?
A Twin Web Agent account and a Make account. The doc lists no prerequisite and no app-specific steps, so the generic Make flow applies: add a module, click Create a connection, name it if you like, then either authorize Make on the app page or paste the key the app provides, and click Save. The same connection then serves both modules, including Make an API Call. If something fails, reopen the connection and check the account it points to.
03Can Twin Web Agent start a Make scenario on its own?
No. The app has no trigger module, scheduled or instant, so nothing in Twin Web Agent can launch a scenario. Start the flow another way: put a trigger from another app first, such as a form or a help desk, or let Make run the scenario on its schedule, which is every 15 minutes by default for a new scenario. Twin Web Agent then acts as the second step, and each new item from that first app reaches it as a bundle.
04What if a Twin Web Agent module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Twin Web Agent API with the connection you already have, which covers what Start a Browsing Task does not. Keep in mind that the Make doc for this app is limited: it says there is not enough public information yet for complete documentation. Rely on whatever API reference Twin Web Agent itself publishes, if any, and test every call with Run once before you switch the scenario on.
05Should Twin Web Agent be automated with Make or n8n?
It depends on the tool your team already runs. On Make, Twin Web Agent offers 2 modules and Make an API Call covers the rest of its API. The same app often has an n8n node as well, so check whether that node exists before choosing. Compare both on the modules each one exposes for this app and on how comfortable your team is with each editor, not on general reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations