Resources · Make integration

602 Sofa Make integrationAutomate 602 Sofa with Make.

Can Make move your 602 Sofa documents and data without a developer? The 602 Sofa Make integration gives you 17 modules: 2 scheduled triggers, 14 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the 602 Sofa Make integration do for you?

The 602 Sofa Make integration links your 602 Sofa account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Each step is a module, one brick that watches, reads or writes something in 602 Sofa, so documents and records reach your other tools without copy and paste.

Documents that travel on their own. Watch Documents spots new documents in 602 Sofa, Download a Document fetches the file, and the next module can store it or send it to a colleague. Upload a Document works the other way, pushing a file from another app into 602 Sofa.

A people directory you can reuse. Get Users, Get Groups and Get Roles read who works in the account, which is handy when another tool needs the same list of people or teams.

Tables that feed your reports. Watch Data Table and Get Data Table read a 602 Sofa data table so a spreadsheet or a dashboard receives its rows. For queries the ready-made modules do not cover, Execute a GraphQL Query lets a technical teammate write the request.

One honest limit: Make's documentation for 602 Sofa is short. It lists the module names but describes none of them, gives no connection steps and says there is not enough public information yet. The notes below read each module from its name, so check the real output with Run once before relying on it. When a run fails, the Make troubleshooting guide helps you read the error.

Weighing another tool? The n8n vs Make comparison sets the two side by side, and the Make pricing page explains how operations are counted.

Connect

How do you connect 602 Sofa to Make?

  1. 01

    Add a 602 Sofa module

    In your scenario, click the +, search for 602 Sofa and pick any of its modules. Then click Create a connection. A connection is your 602 Sofa account linked to Make once, and every 602 Sofa module reuses it afterwards.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the workspace or the team it belongs to. This step is optional, yet it saves confusion the day you link a second 602 Sofa account to the same Make organization.

  3. 03

    Authorize Make and save

    Make then asks you either to approve access on a 602 Sofa page or to paste a key that 602 Sofa gives you; Make's docs do not say which one applies here. Follow the window that opens, then click Save. The connection now shows in the module.

First scenario

Your first scenario with 602 Sofa

GoalWhen a new document appears in 602 Sofa, Make downloads it so the next module can file or share it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the editor to add the very first module.

  2. 02

    Pick Watch Documents

    Search for 602 Sofa, choose Watch Documents and select your connection, or click Create a connection if this is your first 602 Sofa module.

  3. 03

    Add Download a Document

    Click the + to the right of the trigger, pick Download a Document and map the document coming from Watch Documents. Each document arrives as a bundle, one item passed along.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and the bubble above each module shows the bundles it received, so you see exactly what 602 Sofa sends back.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or pick another interval, then switch the scenario on so it keeps running without you.

Triggers

What starts a 602 Sofa scenario?

2 modules start a scenario when something happens in 602 Sofa. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by 602 Sofa as soon as it happens.

602 Sofa1Watch Data Table

Watch Data Table

triggerIn the docs only

Watch Data Table keeps an eye on a data table in 602 Sofa and, judging by its name, hands each new row to the rest of your scenario, so a report or another app stays in step with the table.

How it fires
it is a scheduled trigger, meaning Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan.
When to use it
a team fills a table in 602 Sofa and a spreadsheet or a CRM should receive each entry.
Watch out
the docs do not say whether edited rows count, so test with Run once.
602 Sofa2Watch Documents

Watch Documents

triggerIn the docs only

Watch Documents notices documents added in 602 Sofa and starts your scenario with each one as a bundle, which makes it the natural first module for filing, sharing or archiving paperwork.

How it fires
scheduled, so Make checks the app on the scenario's schedule. Nothing reaches Make between two checks; paid plans can shorten the gap to 1 minute.
When to use it
contracts or forms land in 602 Sofa and a colleague or a storage app needs a copy.
Watch out
Make's docs give no description of this trigger, so confirm with Run once which documents it picks up.
Modules

What can each 602 Sofa module do?

602 Sofa gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

602 Sofa1

Download a Document

ActionIn the docs only

Download a Document gets a document out of 602 Sofa as a file your next module can store, attach to an email or pass to another tool.

When to use it
right after Watch Documents or Search Documents, when you need the content itself rather than a reference to it.
Watch out
on the Free plan Make handles files up to 5 MB, so test with your heaviest document before going live.
602 Sofa2

Download a File

ActionIn the docs only

Download a File retrieves a file held in 602 Sofa so another app can receive it. Its name sets it apart from Download a Document, which suggests 602 Sofa stores files and documents separately.

When to use it
an attachment kept in 602 Sofa has to reach a shared drive or a colleague.
Watch out
the docs do not explain the difference between the two, so compare both outputs with Run once.
602 Sofa3

Execute a GraphQL Query

ActionIn the docs only

Execute a GraphQL Query sends a request you write yourself to 602 Sofa and returns the answer, which covers needs that none of the ready-made modules handles.

When to use it
a teammate who knows the 602 Sofa data model needs a field or a filter the other modules do not offer.
Watch out
this is the most technical module of the list, and Make's docs show no example query to start from.
602 Sofa4

Get Company Features

ActionIn the docs only

Get Company Features reads, by its name, the features switched on for your company in 602 Sofa, giving your scenario a way to check what the account can do before it acts.

When to use it
a scenario shared across several 602 Sofa accounts should behave differently depending on what each one has enabled.
Watch out
run it once and look at the bundle, since the docs describe none of the values returned.
602 Sofa5

Get Data Table

ActionIn the docs only

Get Data Table pulls the content of a 602 Sofa data table on demand, unlike Watch Data Table, which waits for new rows to show up on its schedule.

When to use it
another event, such as a form reply or a message, should trigger a full read of the table.
Watch out
each module run is an operation, the unit Make counts on your plan, so avoid calling it for every bundle when a single read is enough.
602 Sofa6

Get Groups

ActionIn the docs only

Get Groups lists the groups set up in your 602 Sofa account, which lets another tool mirror the same teams without anyone typing them twice.

When to use it
you keep teams in 602 Sofa and want a chat tool, a sheet or a directory to show the same groups.
Watch out
a list can bring back many items at once, so the modules that follow will run once per group.
602 Sofa7

Get Roles

ActionIn the docs only

Get Roles returns the roles defined in 602 Sofa, a useful reference when you audit who can do what or copy permissions into another system.

When to use it
an access review needs the current roles in a spreadsheet instead of screenshots from the admin screen.
Watch out
the module only reads; nothing on Make's page for 602 Sofa suggests it can change a role.
602 Sofa8

Get User by ID

ActionIn the docs only

Get User by ID fetches one precise 602 Sofa user when an earlier module already gave you that person's identifier, so you get their details without a search.

When to use it
a document or a table row points to its author by ID and you want the name to put in a notification.
Watch out
map the ID from the previous module rather than typing it, or the scenario will always return the same person.
602 Sofa9

Get User by Name

ActionIn the docs only

Get User by Name looks up a 602 Sofa user from a name, which is handy when the only thing you know comes from an email, a form or a message.

When to use it
a form asks people for their name and you need to match it to their 602 Sofa account.
Watch out
names are less reliable than IDs; spelling differences or two people with the same name can give a wrong match.
602 Sofa10

Get Users

ActionIn the docs only

Get Users brings back the users of your 602 Sofa account, a starting point for syncing the team with an HR sheet, a mailing list or another directory.

When to use it
a new hire arrives, or a person leaves the company, and you want to compare the 602 Sofa list with the one in another tool.
Watch out
every user comes out as a separate bundle. Anything you place after it therefore runs once per person, and each of those runs costs operations.
602 Sofa11

Search Documents

SearchIn the docs only

Search Documents finds 602 Sofa documents that match your criteria and returns zero, one or several of them, each one as a separate bundle.

When to use it
you need to locate an existing document, for example the one linked to a client, before downloading or updating it.
Watch out
when nothing matches, the modules after it simply do not run, which can look like a silent failure during tests.
602 Sofa12

Start an Agenda

ActionIn the docs only

Start an Agenda launches, as its name says, a new agenda in 602 Sofa from your scenario, so work can begin there when something happens in another app.

When to use it
a signed quote, a new order or a form reply should open a matching case in 602 Sofa without anyone doing it by hand.
Watch out
Make's docs do not say what an agenda holds, so ask your 602 Sofa admin which one to start.
602 Sofa13

Update a Document

ActionIn the docs only

Update a Document changes an existing document in 602 Sofa, which keeps it current when the information lives in another tool.

When to use it
a status or a detail changes in your CRM and the matching 602 Sofa document should follow.
Watch out
an update overwrites what was there; place Search Documents before it so you edit the right document, and test on a copy first.
602 Sofa14

Upload a Document

ActionIn the docs only

Upload a Document places a file coming from another app into 602 Sofa as a document, so paperwork gathered elsewhere lands where your team works on it.

When to use it
an email attachment or a signed PDF from an e-signature tool should be filed in 602 Sofa automatically.
Watch out
map a real file from the previous module, not just its name, or 602 Sofa receives nothing usable.
602 Sofa15

Upload a File

ActionIn the docs only

Upload a File sends a file to 602 Sofa as a plain file rather than a document, the counterpart of Download a File.

When to use it
you want to store an attachment or an export in 602 Sofa without turning it into a document your team edits.
Watch out
the docs do not explain when to prefer it over Upload a Document, so try both with Run once and check where each file appears.
Need help

Need help automating 602 Sofa with Make?

A person reads every message.

FAQ

Common questions about 602 Sofa and Make

01Is the 602 Sofa Make integration free?
Yes, 602 Sofa is a standard app, so it works on Make's Free plan. That plan has limits you will feel quickly: 2 active scenarios, at least 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, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations each month.
02What do you need to connect 602 Sofa to Make?
A 602 Sofa account and a Make account. Make's documentation lists no prerequisite and no specific steps for this app, so the generic flow applies: add a 602 Sofa module, click Create a connection, optionally name it, then either authorize Make on a 602 Sofa page or paste a key the app gives you, and click Save. If you lack the rights, ask your 602 Sofa administrator. The connection is then shared by all 17 modules.
03Does the 602 Sofa trigger react instantly?
No. Both triggers, Watch Data Table and Watch Documents, are scheduled: Make checks 602 Sofa on the scenario's schedule and picks up what changed since the last check. A new scenario runs every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans can go down to 1 minute. There is no instant trigger, the kind an app calls through a webhook, for 602 Sofa.
04What if a 602 Sofa module is missing in Make?
It depends on what you need. 602 Sofa has no Make an API Call module, so you cannot send a free request that way. Execute a GraphQL Query is the closest option: a technical teammate can write a query for data the other 14 actions do not reach. Keep in mind that Make's documentation for this app is limited. If that still falls short, the agency team can look at your case.
05Should you use Make or n8n for 602 Sofa?
It depends on your criteria, not on a ranking. On Make, 602 Sofa comes with 17 modules, including 2 scheduled triggers and a GraphQL module, and the visual editor with Run once suits people new to automation. Many apps also have an n8n node, so check whether one exists for 602 Sofa and compare the modules each tool offers for your use case before choosing. The comparison linked higher on this page lays out the general differences.