Make.com Automation Guide

Make.com is a visual automation tool: you drag modules onto a canvas and connect them into a scenario. The LigoSocial app for Make lets those scenarios publish, schedule and draft LinkedIn posts in your voice, or start when you publish or schedule a post in LigoSocial. Make is a good fit when you want routers, filters and multi-step logic so only the right items become LinkedIn posts.

In Make the app may still appear under its earlier name, LiGo. It is the same app and account.

What you can automate

Triggers (start a scenario from LigoSocial):

• New LinkedIn post published: fires when a post goes live through LigoSocial.
• New LinkedIn post scheduled: fires when a post is added to your schedule.

Actions (LigoSocial does something inside your scenario):

• Publish a LinkedIn post right away.
• Schedule a LinkedIn post for a date, time and time zone.
• Create drafts from an idea: turn a rough idea into three post variants saved to your drafts.
• Repurpose content: turn an article, email or transcript into three LinkedIn post variants.
• Generate post ideas for your profile.
• Find posts: fetch your drafts, scheduled or archived posts, or posts with a given label.

Publishing works on every LigoSocial plan. Triggers, scheduling and the other actions are available on plans that include them; see Billing in the app.

Key terms

• Scenario: the whole automation you build in Make.
• Module: one step in a scenario, such as a trigger, an action or a filter.
• Trigger: the event that starts the scenario, such as a new blog post or a new row in a sheet.
• Action: the work a module does, such as LigoSocial repurposing content.
• Mapping: taking data from an earlier module (for example the text of an email) and placing it in a field of a later one (for example the idea for your drafts).

Step 1: Generate your API key

1. In the LigoSocial web app, click Settings & Support at the bottom of the sidebar, then Settings, then Integrations. Or open https://app.ligosocial.com/settings#integrations.

   

2. Check that LinkedIn shows Connected as under Connect Accounts. Scenarios cannot post without it.

3. Scroll to API Key Management and click Generate API Key. Only the account owner or an admin can do this.

   

4. Copy the key right away and keep it somewhere safe.

The full key is shown only once. Later the card shows Key saved with the first few characters. If you need the key again, click Generate New Key (Replaces Old). The old key stops working, so update every connection that used it (Make, Zapier, Pabbly Connect, Claude and so on).

Step 2: Accept the Make invitation

The LigoSocial app for Make is shared by invitation. Open the Make invitation while signed in to Make and accept it. This installs the app in your Make organization.

Step 3: Connect LigoSocial in a scenario

1. In Make, click Create a new scenario.
2. Click the plus button, search for LigoSocial (or LiGo) and pick a trigger or action.
3. When the module asks for a connection, click Add, paste your API key and save.
4. Map the fields the module needs, then add the rest of your modules.

Example scenarios

New blog post to LinkedIn variants in Slack

1. WordPress: Watch Posts.
2. LigoSocial: Repurpose content, mapping the post content.
3. Slack: Send a Message with the variants, so your team can pick one.

Notion page marked "Ready to Post" to LinkedIn

1. Notion: Watch Events.
2. Filter: status equals Ready to Post.
3. Notion: Get Page Content.
4. LigoSocial: Publish LinkedIn post (or Schedule LinkedIn post, or Create drafts from an idea if you want a review step).

Back up every scheduled post to Google Drive

1. LigoSocial: New LinkedIn post scheduled.
2. Google Drive: save the post text to a folder (or use Google Sheets to add a row).

Weekly review tasks in ClickUp

1. Schedule the scenario to run every Monday.
2. LigoSocial: Find posts, filtered to drafts or a client label.
3. ClickUp: Create a Task for each post, so someone reviews it.

Test before you switch it on

• Right-click a module and choose Run this module only to test it with sample data. This runs for real: testing a publish module publishes a real post on LinkedIn. Test with a drafts action first.
• Make sure the trigger has data to send. For example, if a scenario pulls drafts, have at least one draft in LigoSocial.
• Check the scenario's execution history to confirm the data was mapped correctly and no errors came back.

Troubleshooting

401 or 403 errors. The key is wrong, has been replaced, or the action is not included in your plan. Paste the key again without extra spaces. If you generated a new key in LigoSocial, update the connection in Make. If the message mentions your plan, see Billing in the app.

I can't find the app in Make. Accept the invitation in Step 2 while signed in to the same Make organization, then search again for LigoSocial or LiGo.

Scheduling fails with a date or time error. Format the date as YYYY-MM-DD and include the time zone. Make's date functions can do this in the mapping.

The post did not appear on LinkedIn. Open Settings > Integrations and check the LinkedIn connection. If it is expiring or has expired, click Refresh Connection.

The trigger never fires. Publish or schedule a test post in LigoSocial so the trigger has an event to pick up.

Keep your key safe

• Treat the API key like a password. Do not put it in screenshots, shared documents or public code.
• If it may have leaked, click Generate New Key (Replaces Old) at once and update your connections.
• Give scenarios clear names, for example "WordPress to LinkedIn variants", so they are easy to find and fix.

Common questions

How do I disconnect LigoSocial from Make? In Make, open Connections in the left menu, find the LigoSocial (or LiGo) connection and delete it. To block access completely, also generate a new key in LigoSocial.

Make or Zapier? Make is better when you need routers, filters and multi-step logic. Zapier is quicker to start with. Both use the same LigoSocial actions and API key.

Where are the developer docs? The LigoSocial API reference is at https://ligosocial.com/api-documentation, and the Make overview page is https://ligosocial.com/integrations/make.

Contact support

Use Contact Support under Settings & Support in the sidebar, or the round Contact Support button at the bottom right of the screen (on a computer). You can also email [email protected]. Include the scenario name, the module that failed, the error message and the time it happened. Never send your API key.

Related articles

• Zapier integration: automate LinkedIn tasks with LigoSocial
• Automation with Pabbly Connect
• How to repurpose content