Resources · Make integration

AlphaInsider Make integrationAutomate AlphaInsider with Make.

Can Make send data to AlphaInsider without a line of code? The AlphaInsider Make integration gives you 2 action modules and no trigger. This guide shows how to link your account with an API token, and how to build a first scenario that starts in another app.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AlphaInsider Make integration do?

The AlphaInsider Make integration lets a scenario, the automation you build in Make, act on your AlphaInsider account. It offers two action modules, Create a New Order Webhook and Make an API Call. A module is one brick of the scenario. Since AlphaInsider has no trigger, something else has to start the run.

Push orders from another tool. When a signal comes out of another app, the next module in the chain can be Create a New Order Webhook. The official doc gives no description of this module, so read its fields in the editor once your connection exists, and test it before you rely on it.

Reach what the modules do not cover. Make an API Call calls any endpoint of the AlphaInsider API with the same connection. It is the way out when the single dedicated module is not enough for your case.

Start on a schedule. With no trigger, you can also launch the scenario from the clock on its first module. A new scenario runs every 15 minutes by default.

What Make does not do here: there is no module that watches AlphaInsider and starts a scenario on its own, and the doc lists no search module. The doc also warns that its own content is AI-generated and may contain mistakes, so check important details with AlphaInsider. The same app may exist as an n8n node; the n8n vs Make comparison helps you choose. To learn the editor step by step, see our Make training, and when a run fails, open Make troubleshooting.

Connect

How do you connect AlphaInsider to Make?

  1. 01

    Generate your API key

    In AlphaInsider, open the developer settings page from the account menu, click the button that generates a new API key, then copy the key shown on screen. Your token needs the newOrderWebhook permission, and you need an active AlphaInsider account first.

  2. 02

    Add the module and create the connection

    In your Make scenario, add an AlphaInsider module and click Create a connection. A connection is your AlphaInsider account linked to Make once, then reused by both modules of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional; a clear name helps when you run several accounts. Paste the API key you copied, or follow the instructions on screen.

First scenario

Your first scenario with AlphaInsider

GoalWhen another app sends new data, Make passes it to AlphaInsider with Create a New Order Webhook.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app whose data should start the flow, since AlphaInsider has no trigger.

  2. 02

    Add the AlphaInsider module

    Click the + on the right of that first module, search for AlphaInsider and pick Create a New Order Webhook. Click Create a connection and paste your API key.

  3. 03

    Map the fields

    Fill the module fields and map values from the previous module. Each item passed along is a bundle: one row, one record, one message from the first app.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received, including what AlphaInsider sent back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the AlphaInsider modules do

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

AlphaInsider1

Create a New Order Webhook

ActionIn the docs only

This is the dedicated AlphaInsider action, and the one your API token must be allowed to use through the newOrderWebhook permission. The official doc gives it no description, so its exact behavior is something to confirm in the editor.

When to use it
place it after a module of another app that produces the data you want to hand over to AlphaInsider.
Watch out
run it with Run once and read the returned bundle before you switch the scenario on.
AlphaInsider2

Make an API Call

ActionIn the docs only

Here you get the whole AlphaInsider API from one module: pick an endpoint, send the request, and Make uses the connection you already created. Nothing else to set up on the account side.

When to use it
the moment you need an AlphaInsider feature that Create a New Order Webhook does not offer.
Watch out
the Make doc does not list the endpoints, so keep the AlphaInsider API reference open while you fill the request.
Need help

Need help automating AlphaInsider with Make?

A person reads every message.

FAQ

AlphaInsider and Make: frequent questions

01Is the AlphaInsider Make integration free?
Yes, on the Make side. AlphaInsider is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your AlphaInsider subscription is a separate matter: the doc points to the AlphaInsider pricing page for it.
02What does the AlphaInsider Make integration need to connect?
An active AlphaInsider account and an API token that carries the newOrderWebhook permission. You generate the key from the developer settings page, reached through the account menu, then copy it. In Make, add an AlphaInsider module, click Create a connection, give it a name if you like and paste the key. The connection is then shared by both modules of the app, so you only do this once per account.
03Does the AlphaInsider integration react in real time?
No, because AlphaInsider has no trigger in Make: no module watches the account and starts a scenario for you. You start the flow another way. Either a trigger from another app opens the scenario and the AlphaInsider module follows it, or you set a schedule on the first module, every 15 minutes by default, or every minute at the fastest on a paid plan. How quickly things move then depends on that first module.
04What if an AlphaInsider module is missing in Make?
Use Make an API Call. It reaches any endpoint of the AlphaInsider API with the connection you already have, so a missing action does not block you. Fill the request from the AlphaInsider API reference and test it with Run once. Keep in mind that the Make doc for this app warns that its content is AI-generated and may contain mistakes, so confirm important details directly with AlphaInsider before you build on them.
05Is Make or n8n better for AlphaInsider?
It depends on the tool your team already knows. The same app often has an n8n node, so check whether it exists before deciding. On Make, you get 2 modules, a connection built from an API token and a visual editor where Run once shows each bundle. On n8n, look at what its node covers and compare it with Create a New Order Webhook and Make an API Call. Pick the one that covers your case.