Resources · Make integration

Social by Greenwood Apps Make integrationAutomate Social by Greenwood Apps with Make.

Turn content from your other tools into social posts without copying and pasting. The Social by Greenwood Apps Make integration gives you 10 modules: 1 trigger, 6 actions and 3 searches. This page shows how to link your account and build a first scenario, step by step.

Try the Social by Greenwood Apps integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Social by Greenwood Apps Make integration do?

It lets Make, a no-code automation tool, read and write your Social by Greenwood Apps posts for you. You build a scenario (the automation itself, a chain of bricks called modules) that creates posts, groups them in bulk sessions or reacts when a new post shows up, and passes the result to your other apps.

Posts that write themselves from another app. Put a module from your blog, spreadsheet or form tool first, then Create a Post. Each new item that lands there becomes a post in Social by Greenwood Apps, with the text mapped from the previous module.

A batch of posts in one go. When a campaign needs several posts at once, Add Posts to Bulk Session files them into one bulk session, and Get Bulk Post Session or List Bulk Post Sessions lets you check what the session holds before anything goes out.

A log of what was published. Watch Posts picks up new posts at each scheduled check, so you can copy it to a sheet, notify the team or archive it. List Posts and Get a Post fetch older ones on demand.

Be aware that the official Make documentation for this app is limited: it lists the modules but gives no field descriptions, no connection steps and no usage limits. Test every module with Run once before relying on it. If you also use n8n, the same app may have a node there too; the n8n vs Make comparison helps you pick a tool, while the Make review and Make pricing pages cover the platform itself.

Connect

How do you connect Social by Greenwood Apps to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any Social by Greenwood Apps module, then click Create a connection. A connection is your account linked to Make once and reused by every module of the app, so you only do this step one time.

  2. 02

    Give the connection a name

    This field is optional, but a clear name like the brand or client account saves confusion later when several connections sit side by side in the same list.

  3. 03

    Authorize Make and save

    Either approve Make on the Social by Greenwood Apps authorization page or paste the key the app gives you, depending on what the window asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Social by Greenwood Apps

GoalWhen a new item lands in another app, Make turns it into a post in Social by Greenwood Apps.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. This first brick is the app where your content comes from.

  2. 02

    Pick the source module

    Search your source app by name, choose the module that watches for new items, connect the account and fill its fields. Make lists the folders or sheets it can read.

  3. 03

    Add Create a Post

    Click the + on the right of the first module, search Social by Greenwood Apps, pick Create a Post and create the connection. Map the text from the first module into the post fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles (the items passed from module to module) each step received. Check the post that came out.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Save, then switch the scenario on.

Triggers

What starts a Social by Greenwood Apps scenario

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

Social by Greenwood Apps1Watch Posts

Watch Posts

triggerIn the docs only

You get a scenario that picks up new posts from your Social by Greenwood Apps account and hands each one to the next module as a bundle, ready to log or share. The documentation only names it, so you discover its filters in the editor.

How it fires
scheduled: Make checks the app on the scenario's schedule. The module name points to a polling trigger, so check for the clock badge when you add it.
When to use it
the team publishes by hand and you want every new post copied to a sheet or a chat channel.
Watch out
if Create a Post follows it in the same scenario, the posts it creates will likely be picked up at the next check too.
Modules

What each Social by Greenwood Apps module does

Social by Greenwood Apps gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Social by Greenwood Apps1

Add Posts to Bulk Session

ActionIn the docs only

Drop several posts into one bulk session so a whole campaign travels as a single group instead of scattered drafts. The name says it adds to an existing session, so you pick that session first.

When to use it
a product launch where a row of texts from a spreadsheet should become one batch.
Watch out
the documentation gives no field list, so run it once on a test session before a real one.
Social by Greenwood Apps2

Create a Post

ActionIn the docs only

Produces one new post in your account from data mapped out of the previous module, which is the core of most scenarios with this app. Reach for it when you want one post per incoming item rather than a grouped batch.

When to use it
each new blog article or form answer should become its own post.
Watch out
Make counts one operation per post created, so a busy source adds up fast on the Free plan.
Social by Greenwood Apps3

Get Bulk Post Session

ActionIn the docs only

Brings back the details of one bulk session you already know, so the next modules can read what it contains. Although Make files it as an action, it reads rather than changes anything, going by its name.

When to use it
right after Add Posts to Bulk Session, to confirm the batch looks right before you notify anyone.
Watch out
it needs the session identifier, usually mapped from List Bulk Post Sessions.
Social by Greenwood Apps4

Get Post Options

ActionIn the docs only

Fetches the choices the app offers for a post, judging by its name, so you can check what is available before Create a Post runs. The documentation says nothing more about what comes back, which is why a test run matters here.

When to use it
when you are unsure which values a post accepts and want to see them in the bundle.
Watch out
read its output with Run once before mapping anything from it.
Social by Greenwood Apps5

Get a Post

ActionIn the docs only

Retrieves one specific post with the data Social by Greenwood Apps stores for it, which is handy when a scenario only has the post reference and needs the full content. Pick it over List Posts when you already know exactly which post you want.

When to use it
after Watch Posts, to enrich the new post before sending it to a sheet.
Watch out
map the post identifier from an earlier module, not a typed value.
Social by Greenwood Apps6

List Accounts

SearchIn the docs only

Returns, going by its name, the social accounts linked to your Social by Greenwood Apps workspace, one bundle per account, so the scenario can decide where posts go. As a search, it may return zero, one or several bundles.

When to use it
an agency setup where each client has its own account and posts must be routed to the right one.
Watch out
the next module runs once per account returned, which multiplies operations.
Social by Greenwood Apps7

List Bulk Post Sessions

SearchIn the docs only

Shows the bulk sessions that exist in your account, giving you the identifiers the other bulk modules need. Choose it over Get Bulk Post Session when you do not yet know which session to open.

When to use it
first in a scenario that adds posts to your latest campaign batch, so you know which one to target.
Watch out
if it finds no session, the next modules have nothing to work on for that run.
Social by Greenwood Apps8

List Posts

SearchIn the docs only

Pulls a list of your posts, one bundle each, so you can export, audit or copy them in a single run instead of fetching them one by one. It is a search module, so the result can be empty or long.

When to use it
filling a reporting sheet with every post the account holds after you first connect it.
Watch out
each returned post triggers the following modules, so test on a small account first.
Social by Greenwood Apps9

Make an API Call

ActionIn the docs only

Opens any endpoint of the Social by Greenwood Apps API from your scenario, using the same connection as the other modules. It covers whatever the nine listed modules leave out, provided you know the API.

When to use it
you need a feature that exists in the app but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the app's API documentation open while you set it up.
Need help

Need help automating Social by Greenwood Apps with Make?

A person reads every message.

FAQ

Social by Greenwood Apps and Make: common questions

01Is the Social by Greenwood Apps Make integration free?
Yes, you can use it on the Free plan, because Social by Greenwood Apps is a standard app in Make and not reserved for Enterprise. The Free plan still has limits: 2 active scenarios, a 15 minute minimum 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. Your Social by Greenwood Apps subscription is a separate matter that this page does not cover.
02What do you need to connect Social by Greenwood Apps to Make?
You need a Social by Greenwood Apps account and a Make account. The Make documentation lists no other prerequisite and no official connection steps for this app, so you follow the generic flow: add a module, click Create a connection, optionally name it, authorize Make on the app page or paste the key the app gives you, then click Save. The connection is stored once and every module of the app reuses it.
03Does Watch Posts react in real time?
No, it works on a schedule. Watch Posts is a scheduled trigger, going by its name, so Make checks Social by Greenwood Apps each time the scenario runs rather than being called by the app. A new scenario runs every 15 minutes by default. On a paid plan you can shorten that to 1 minute; on the Free plan 15 minutes is the floor. Look for the clock badge on the module to confirm the type once you add it.
04What if a Social by Greenwood Apps module is missing in Make?
Use Make an API Call. This module lets a scenario call any endpoint of the Social by Greenwood Apps API with the connection you already have, which covers features that the other 9 modules do not expose. Keep in mind that the Make documentation for this app is limited: it names the modules but describes neither their fields nor their limits, so test each module with Run once and read the bundles before building a long scenario on top.
05Make or n8n for Social by Greenwood Apps?
It depends on the tool you already run. On Make, the app offers 10 ready-made modules: 1 trigger, 6 actions and 3 searches, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node as well, so check the n8n side before deciding. If your other automations already live on one platform, keeping Social by Greenwood Apps there saves you from juggling two accounts and two sets of connections.
Same platform

Other docs you might need on this stack.

Browse all integrations