Resources · Make integration

Scriberr Make integrationAutomate Scriberr with Make.

Can Make act on Scriberr for you without a line of code? The Scriberr Make integration offers 2 modules: one trigger and one API call. This page is for teams new to Make, and it walks you from the connection to a first working scenario.

Try the Scriberr integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Scriberr Make integration let you automate?

The Scriberr Make integration links your Scriberr account to Make so a scenario (the automation you build, a chain of modules) can start from Scriberr and send requests back to it. It has two modules, a module being one brick of that chain: a scheduled trigger and a general API call.

Start a flow from Scriberr. Watch Copied Person is the entry point. Make checks Scriberr on the schedule of your scenario and hands each new result to the next module as a bundle, one item passed along the chain.

Reach what the list does not show. Make an API Call reuses your Scriberr connection to call any endpoint of the Scriberr API. It is the door for everything the trigger alone does not cover.

Hand the result to your other tools. After those two modules, you can add any other app from Make to the same scenario, so the data from Scriberr lands where your team already works.

Know the limit before you start: Make itself says its documentation for Scriberr is limited, because little public information exists about the app. Plan to test each step with Run once. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make troubleshooting guide helps when a run fails. To learn the editor properly, see the Make training.

Connect

How do you connect your Scriberr account to Make?

  1. 01

    Open the connection window

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

  2. 02

    Authorize Make on Scriberr

    Give the connection a name if you like, so you recognize it later. Then either approve Make on the Scriberr page that opens, or paste the key that Scriberr gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and you can pick it in any other Scriberr module you add to this scenario or to the next ones.

First scenario

Build your first scenario with Scriberr

GoalWhen a copied person shows up in Scriberr, Make picks it up and sends a follow-up request to the Scriberr API.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. This first module is what starts the whole flow.

  2. 02

    Add the trigger

    Search for Scriberr, pick Watch Copied Person, then click Create a connection or Add to link your account as shown above.

  3. 03

    Chain the API call

    Click the + on the right of the trigger and pick Make an API Call. Fill in the request and map data from the bundle the trigger returns.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Fix what looks wrong before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. It now runs by itself.

Triggers

What starts a Scriberr scenario

1 module starts a scenario when something happens in Scriberr. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Scriberr as soon as it happens.

Scriberr1Watch Copied Person

Watch Copied Person

triggerIn the docs only

This trigger gives your scenario a starting point inside Scriberr: each new result it finds becomes a bundle that the next modules can use. Make's documentation gives no description of it, so its exact behavior is best confirmed with a first test.

How it fires
scheduled, as far as its name suggests, since Make's documentation does not state the type. Make checks the app on the scenario's schedule, which is every 15 minutes by default, and at most once every 15 minutes on the Free plan.
When to use it
as the first module whenever the flow should begin from Scriberr rather than from another app.
Watch out
click Run once before switching the scenario on, and read the bundle it returns to see which data you can map.
Modules

What else Scriberr can do in Make

Scriberr gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Scriberr1

Make an API Call

ActionIn the docs only

You get access to any endpoint of the Scriberr API from inside your scenario, using the connection you already set up. No second login is needed.

When to use it
when the trigger alone does not give you the action you need, since this is the only action module the app offers.
Watch out
Make's documentation for Scriberr is limited, so build the request one small step at a time and test it with Run once.
Need help

Need help automating Scriberr with Make?

A person reads every message.

FAQ

Scriberr and Make: common questions

01Is the Scriberr Make integration free?
Yes. Scriberr is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one operation being one module running on one bundle.
02What do you need to connect Scriberr to Make?
A Scriberr account and a Make account. Make's documentation lists no specific prerequisite for Scriberr and gives no official connection steps. The generic path applies: add a Scriberr module, click Create a connection, name it if you want, authorize Make on the Scriberr page or paste the key Scriberr provides, then click Save. The same connection serves both modules. If you are unsure which option the window shows, open it once and read it before filling anything in.
03Does the Scriberr trigger in Make work in real time?
Most likely not. Make's documentation does not state the type of Watch Copied Person, but its name points to a scheduled trigger, the kind marked with a clock badge in the editor. Make checks Scriberr on the scenario's schedule, which is every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; on paid plans it can go down to 1 minute. An instant trigger, called by the app through a webhook, does not exist for Scriberr. If a delay of a few minutes matters for your process, keep this in mind when you design the scenario.
04What if the Scriberr module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Scriberr API with the connection you already have, so it covers what the trigger does not. Keep in mind that Make describes its own Scriberr documentation as limited, because little public information about the app is available. Start with a simple request and test every request with Run once before you switch the scenario on. The Make troubleshooting guide linked higher on this page also helps when a request fails.
05Should you use Make or n8n for Scriberr?
It depends on the tool your team already knows. In Make, Scriberr offers 2 modules: a scheduled trigger and an API call, and it works on the Free plan. The same app may also have an n8n node, so check what each tool actually lists for Scriberr before choosing. Compare the modules on offer and how your team likes to build, rather than a general ranking of the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations