Resources · Make integration

SEEN Make integrationAutomate SEEN with Make.

Can Make watch SEEN for new videos and create new ones for you? The SEEN Make integration offers 3 modules: 1 trigger and 2 actions. This guide is for teams who already use SEEN and want to wire it to their other tools, one clear step at a time.

Try the SEEN integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SEEN Make integration do for you?

The SEEN Make integration links your SEEN account to Make, a visual tool where you build a scenario: the automation itself, made of modules placed one after the other. Each module is one brick, such as a trigger that starts things or an action that does something in SEEN.

Start a video from another tool. A request lands in a form or a spreadsheet, and Create a video asks SEEN for a new one without anyone opening SEEN. That is the scenario walked through below.

React when a video appears. Watch for created video spots new videos in SEEN, and each one travels to the next module as a bundle, a single item Make hands down the chain. From there you can alert a colleague or log the video in another app.

Reach what the list does not cover. Make an API Call sends any request to the SEEN API with the same connection, which helps when the two other modules stop short.

Be aware of one real limit: Make states that its SEEN documentation is incomplete, because public information about the app is scarce. Expect to discover the fields inside the editor rather than on paper. If a run fails and you cannot see why, Make troubleshooting walks through the usual checks. Still weighing tools? The n8n vs Make comparison lays out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect SEEN to Make?

  1. 01

    Add a SEEN module

    In your scenario, add any SEEN module and click Create a connection. A connection is your SEEN account linked to Make once, then reused by every SEEN module you add later.

  2. 02

    Name it and authorize

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

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and Make can list what it is able to read from your account. If that list stays empty, check that you signed in with the right SEEN account.

First scenario

Build your first scenario with SEEN

GoalWhen a new request lands in another app, Make asks SEEN to create a video.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. This first module is the starting point: the app where your video requests arrive.

  2. 02

    Set the starting module

    Pick the app that holds your requests, such as a form tool or a spreadsheet, and choose its module that reacts to a new entry. Connect that account the same way you connect SEEN.

  3. 03

    Add Create a video

    Click the + on the right of the first module, search for SEEN and pick Create a video. Link your SEEN connection, then map the data from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Add a test entry in the first app, then click Run once. Open the bubble above each module to read the bundles it received and confirm SEEN got what you expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. Each module run on one bundle counts as an operation on your Make plan.

Triggers

What starts a SEEN scenario

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

SEEN1Watch for created video

Watch for created video

triggerIn the docs only

This trigger hands you every new video created in SEEN, one bundle per video, so the rest of your scenario can act on it without anyone checking SEEN by hand.

How it fires
scheduled: Make checks the app on the scenario's schedule. The doc gives no type for this module, so this reading comes from its name; the clock badge on the module in the editor confirms it.
When to use it
you want a colleague alerted, or a record added elsewhere, whenever a fresh video shows up in SEEN, picked up at the next check.
Watch out
with no official description, run it once and read the bundle before mapping anything downstream.
Modules

What the SEEN modules do

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

SEEN1

Create a video

ActionIn the docs only

Create a video lets another tool order a new SEEN video, so requests collected elsewhere become videos without a person copying details across.

When to use it
a lead fills a form or a row lands in a sheet, and that event should produce a video.
Watch out
Make publishes no field list for it, so open the module after connecting and see which inputs it actually asks for.
SEEN2

Make an API Call

ActionIn the docs only

Make an API Call is your escape hatch: it reaches any endpoint of the SEEN API while reusing the connection you already set up, no second login needed.

When to use it
you need something that neither Watch for created video nor Create a video offers.
Watch out
this module expects you to know the SEEN API request you want to send, and Make gives no SEEN specific help for it.
Need help

Need help automating SEEN with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the SEEN Make integration free?
Yes, SEEN is a standard app, so its modules work on the Make Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two 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) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. This page does not cover what SEEN itself costs.
02What do you need to connect SEEN to Make?
A SEEN account and a Make account. Make lists no special prerequisite for SEEN and publishes only its generic connection flow: add a SEEN module, click Create a connection, optionally name it, then either approve Make on the SEEN page or paste the key SEEN provides, and click Save. The connection is stored once and every SEEN module in your scenarios reuses it. If something looks different from this flow, trust what the window asks for.
03Does the SEEN Make trigger react in real time?
No, not as far as the documentation shows. Watch for created video is treated as a scheduled trigger, a reading based on its name since the doc gives no type. Make checks SEEN on the scenario's schedule, every 15 minutes by default, and no sooner than 15 minutes on the Free plan or 1 minute on a paid plan. A new video is picked up at the next check, not the instant it appears. The clock badge on the module confirms the type.
04What if a SEEN module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the SEEN API with the connection you already have, so you are not stuck with the two listed actions and the one trigger. Keep in mind that Make says its SEEN documentation is limited, because little public information about the app exists. You will need the SEEN API reference to build that request, and testing it with Run once before switching the scenario on is the safest path.
05Should you use Make or n8n for SEEN?
It depends on where the rest of your automations already live. Make gives SEEN 3 modules here: 1 scheduled trigger and 2 actions, including a generic API call. Many apps also have an n8n node, so check whether SEEN does before deciding. Neither tool is ranked here: compare which modules each one offers for SEEN, how your team already works, and which editor feels clearer to the people who will maintain the scenario over time.
Same platform

Other docs you might need on this stack.

Browse all integrations