Resources · Make integration

TwitterShots Make integrationAutomate TwitterShots with Make.

Need a clean image of a tweet without taking screenshots by hand? The TwitterShots Make integration gives you 3 action modules and no trigger. This guide shows how to link your account, what each module is for and how to build a first working scenario.

Try the TwitterShots integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TwitterShots Make integration do for you?

The TwitterShots Make integration lets a Make scenario, the automation you build as a chain of modules, ask TwitterShots for a screenshot of a tweet. You get either a file or a link, ready for the next step, and you never open a browser to crop an image yourself.

A link for a shared list. A social media manager collects tweet links in a spreadsheet. The scenario reads each new row, sends it to Create a Tweet Screenshot (URL) and writes the image link back, so the team sees the visual next to the source.

A file for your archive. A press office wants a copy of every mention it tracks. Create a Tweet Screenshot (File) returns something a storage app can save in a folder, instead of a link that points elsewhere.

A custom call for the odd case. When neither of those two fits, Create Tweet Screenshot With API Request is, going by its name, the module for a request you shape yourself.

Know the limits before you start. Make states that its documentation for TwitterShots is incomplete because little public information exists about the app, and the app has no trigger: something else has to start the scenario. Test every module with Run once before you rely on it. If you are new to the editor, the Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a platform.

Connect

How do you connect TwitterShots to Make?

  1. 01

    Add a TwitterShots module

    In your scenario, click the + and search for TwitterShots. Pick any of its modules, then click Create a connection. A connection is your TwitterShots account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when you run several accounts. Then either authorize Make on the TwitterShots page that opens, or paste the key TwitterShots gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and the other two TwitterShots modules will offer it in their list, so you only do this once per account.

First scenario

Your first scenario with TwitterShots

GoalWhen a new tweet link shows up in another app, Make asks TwitterShots for a screenshot and hands you back its link.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since TwitterShots has no trigger, start with the app where your tweet links live.

  2. 02

    Set up the source module

    Pick the module of that app that returns new items and fill its fields. Each item it sends on is a bundle: one row, one message, one link that flows to the next module.

  3. 03

    Add Create a Tweet Screenshot (URL)

    Click the + on the right of the first module, search TwitterShots and choose Create a Tweet Screenshot (URL). Select your connection, then map the tweet link from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received and check what TwitterShots sent back.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Modules

What the TwitterShots modules do

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

TwitterShots1

Create Tweet Screenshot With API Request

ActionIn the docs only

This one is your escape hatch. Judging by its name, it lets you send TwitterShots a request you build yourself, which is useful when the two ready-made screenshot modules do not expose the option you need.

When to use it
after you tried the File and URL modules and found that your case needs something they do not offer.
Watch out
Make's documentation for this app is incomplete, so run it once and read the returned bundle before you connect anything after it.
TwitterShots2

Create a Tweet Screenshot (File)

ActionIn the docs only

You end up with the screenshot as a file inside your scenario, as the module name indicates, so the next module can store it, attach it or pass it along without fetching anything from a link.

When to use it
the next step is a storage app or an email that expects an actual file, such as an archive of mentions.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size in the bundle during your Run once test.
TwitterShots3

Create a Tweet Screenshot (URL)

ActionIn the docs only

Here the result is a link to the screenshot rather than the image itself, which keeps the scenario light when you only need to point people to the visual or save a reference.

When to use it
a spreadsheet row, a chat message or a task card should show where the image lives.
Watch out
the documentation says nothing about how long that link stays available, so open it after your Run once test before you share it widely.
Need help

Need help automating TwitterShots with Make?

A person reads every message.

FAQ

Common questions about TwitterShots in Make

01Is the TwitterShots Make integration free?
Yes, on the Make side. TwitterShots is a standard app, so its modules are available from the 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. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one execution of one module on one bundle. Any cost on the TwitterShots side is separate and not covered here.
02What do you need to connect TwitterShots to Make?
A TwitterShots account and a Make account. The official documentation lists no prerequisites and no specific steps, so the generic Make flow applies: add a TwitterShots module, click Create a connection, optionally name it, authorize Make on the TwitterShots page or paste the key the app provides, then click Save. The connection is created once and every TwitterShots module in your scenarios can reuse it. If something fails, start by checking the account details on the TwitterShots side.
03Can TwitterShots start a Make scenario in real time?
No. TwitterShots has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. You start the flow another way. Either place a trigger from the app that holds your tweet links in first position, or rely on the scenario schedule, which runs every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. The TwitterShots module then runs each time the scenario does.
04What if a TwitterShots module is missing or a limit gets in the way?
It depends on the need. TwitterShots has no Make an API Call module, so there is no generic module to reach beyond the 3 listed here. Going by its name, Create Tweet Screenshot With API Request is likely the most flexible of the three, so try it first. Make also notes that its documentation for this app is incomplete, which means testing with Run once matters more than usual. If the gap remains, another app may cover the step, or the team can look at your case with you.
05Should you use Make or n8n for TwitterShots?
It depends on the platform you already run. Make offers TwitterShots as 3 ready-made action modules that you place in a visual scenario and test with Run once, which suits someone who wants the link or file without writing code. n8n often has its own node for the same apps, so check whether one exists for TwitterShots before deciding. This page makes no claim about speed or cost between the two. The comparison page linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations