Resources · Make integration

RankYak Make integrationAutomate RankYak with Make.

Every article RankYak publishes can set off the next step on its own. The RankYak Make integration gives you 1 module, a trigger that watches published articles. This page is for content and marketing teams: it shows how to link your account, build a first scenario and test it.

Try the RankYak integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RankYak Make integration do for you?

The RankYak Make integration lets Make notice the articles you publish in RankYak and pass each one to the rest of your tools. It works through a scenario, the automation you build in Make, made of modules, the bricks of that automation. RankYak brings one brick: the trigger Watch published articles.

Tell the people who care. A marketing team wants the sales reps to know when a new article is live. Watch published articles picks it up, and a module of your messaging app, added right after it, posts the news where the team already reads.

Keep a log of what went out. An agency running several blogs needs one place that records every article. Put a spreadsheet module behind the trigger and each publication lands as a new row, without anyone copying links by hand.

Start the promotion work. A solo founder who publishes through RankYak can pass each new article to a task or social tool, so the sharing step is never forgotten.

Be clear about the limits. Make's documentation for RankYak is short: it says there is not enough public information to describe the app in full. RankYak offers a trigger only, with no action and no search, and no Make an API Call module, so Make cannot create or edit articles in RankYak. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick. To learn the editor itself, see our Make training, or check Make pricing before you scale.

Connect

How do you connect your RankYak account to Make?

  1. 01

    Add the RankYak module

    In a scenario, click the +, search for RankYak and pick Watch published articles. Then click Create a connection. A connection is your RankYak account linked to Make once, and reused by every RankYak module afterwards.

  2. 02

    Name the connection

    This step is optional, but a clear name helps when you run several RankYak accounts, one per client or per site. Pick something you will recognize later in the connection list.

  3. 03

    Authorize and save

    Authorize Make on the RankYak page that opens, or paste the key RankYak gives you, depending on what the window asks. Then click Save. The module is now tied to your account.

First scenario

Your first scenario with RankYak

GoalWhen RankYak publishes a new article, Make sends it to another app of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to place the first module.

  2. 02

    Place the trigger

    Search for RankYak, choose Watch published articles and pick the connection you made earlier. This module opens the flow: nothing runs until it finds an article.

  3. 03

    Add the next app

    Click the + on the right of the trigger and add a module of the app that should receive the article. Map the article data from the trigger into its fields.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received, one bundle per article found.

  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. From there Make checks RankYak on its own.

Triggers

What starts a RankYak scenario?

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

RankYak1Watch published articles

Watch published articles

triggerIn the docs only

This trigger hands you each article RankYak has published, as a bundle ready to send wherever your team works. It is the only RankYak module in Make, so every scenario built on the app starts here.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, and 15 minutes at the shortest on the Free plan.
When to use it
as soon as a published article should trigger something outside RankYak, such as a message, a row or a task.
Watch out
Make's documentation for this app is limited, so run it once and read the bundles to see what data comes through before you map anything.
Need help

Need help automating RankYak with Make?

A person reads every message.

FAQ

Questions about the RankYak Make integration

01Is the RankYak Make integration free?
Yes, on the Make side. RankYak is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, which are operations, meaning one module running on one bundle.
02What do you need to connect RankYak to Make?
You need two things: a RankYak account and a Make account. Make's documentation lists no prerequisite for this app and gives no dedicated connection steps, so the generic path applies: add the module, click Create a connection, optionally name it, authorize Make on the RankYak page or paste the key RankYak gives you, then click Save. The connection is then reused by every RankYak module in your scenarios, so you only set it up once.
03Does the RankYak trigger in Make work in real time?
No. The documentation does not describe the module, but its name marks it as a scheduled trigger: Make checks RankYak on the scenario's schedule rather than being called by the app. A new scenario runs every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. So an article appears in your scenario at the next check, not the moment it goes live. Run once lets you check the result by hand while you build.
04What if the RankYak Make integration lacks the module you need?
It depends on what you want. RankYak has a single trigger in Make and no Make an API Call module, so Make cannot publish, edit or search articles in RankYak. If you need that, look at whether another app in your stack covers the step, or ask the team for help designing the flow. The documentation itself notes that public information on RankYak is limited, which is probably why the module list is so short.
05Make or n8n for RankYak?
It depends on your tools and habits. Make offers RankYak as a single scheduled trigger that watches published articles, available from the Free plan. The same app often has an n8n node as well, so the fair test is to compare what each side offers for RankYak, plus which platform the rest of your automations already run on. Nothing in the documentation ranks one above the other for this app.
Same platform

Other docs you might need on this stack.

Browse all integrations