Who This Guide Is For
This documentation is designed for LiGo users who:
Want to streamline their LinkedIn management through automation.
Hold an active, paid LiGo subscription.
Are looking for a way to link LiGo with external third-party applications.
By the end of this guide, you will understand how to secure your connection, build your first automated scenario, and troubleshoot common issues.
If you haven't yet, click here to accept your invite link to the Make.com integration.
What is Make.com?
Make.com is a visual automation platform like Zapier & Pabbly Connect that allows you to connect various applications to create automated workflows. It offers a visual canvas where you can drag and drop different modules to design how data flows between your apps.
For LiGo users, this means you can connect your LinkedIn content creation process to hundreds of other tools, such as CRM systems, cloud storage, and note-taking apps.
Capabilities of the LiGo Integration
Once you have linked your LiGo account to Make.com, you can automate several core tasks:
Content Management: Automatically draft, schedule, and publish posts to LinkedIn.
Cotent Repurposing: Convert long-form articles or documents into multiple LinkedIn-optimized posts.
Idea Generation: Create new post ideas or prompts based on data from other apps.
Data Retrieval: Pull your existing drafts, scheduled items, or archived posts into other platforms for reporting or review.
Input Automation: Save content ideas or drafts into LiGo directly from sources like Google Sheets, Outlook emails, etc.
Requirements for Setup
To begin the integration process, ensure you have the following:
LiGo Subscription: An active paid plan is required to access API features.
API Key: You must generate a unique API key from your LiGo account settings.
Platform Invite: You must accept the official LiGo invite link for Make.com to enable the app in your dashboard.
Understanding Key Automation Terms
If you are new to Make.com, it is helpful to understand these basic concepts:
Scenario/Workflow: This refers to the entire automated workflow you build.
Trigger: The event that starts the automation, such a new email, or a new ClickUp message.
Action: The specific task performed by the automation, such as generating a post through LiGo.
Module: Each trigger, action or filter inside Make.com is called a module.
Mapping: The process of taking data from a previous step (like the text of an email) and placing it into a specific field (Post Idea) in LiGo.
Step-by-Step Connection Guide
Follow these steps to link your accounts:
Obtain Your Key: Log in to LiGo, go to your account settings, and copy your API key.
Accept the Invite: Click the LiGo invite link for Make.com to add the LiGo module to your account.
Create a New Scenario: In your Make.com dashboard, click Create Scenario".
Search LiGo: Click the plus icon, search for LiGo, and select any one of the triggers.
Authenticate: When prompted, click Add Connection. Enter your LiGo API key that you just copied into this field and hit save.
Example Automations
Automation #1: WordPress → LiGo → Slack
Use case: Repurpose new Wordpress posts into LinkedIn post variants & send them to your Slack channel for approval.
Setup:
Trigger: WordPress -> Watch Posts
Action: LiGo -> Repurpose Content
Actions: Slack -> Send a Message
How it works:
Every time a new post is created in WordPress, the post's content is sent to LiGo. LiGo then repurposes this post into multiple different LinkedIn post variants. These variants are then sent to your Slack channel.
Automation #2: Notion → LiGo
Use case: Everytime a page's status is changed to "Read to Post", the page is published to LinkedIn.
Setup:
Trigger: Notion -> Watch Events
Filter: Equal to Ready to Post
Action: Notion -> Get Page Content
Action: LiGo -> Publish LinkedIn Post
How it works:
When a page is marked as "Ready to Post", the page's content is scraped and sent to LiGo. It then publishes your post to LinkedIn.
Automation #3: LiGo→ Google Drive
Use case: Post scheduled to LinkedIn? The post's content is saved to your drive.
Setup:
Trigger: LiGo -> New LinkedIn Post Scheduled
Action: Slack -> Create a File/Folder Shortcut
How it works:
Whenever you schedule a new post, Make sends it to your Google drive folder to ensure that your data always remains backed up.
Automation #4: LiGo → ClickUp
Use case: Fetch posts on regular intervals and create a task to review it.
Setup:
Trigger: LiGo -> Fetch Posts by Category
Action: ClickUp -> Create a Task
How it works:
Posts are fetched from your LiGo account, they are then sent to ClickUp & a task is created to review them. The time interval can be set by you.
Testing & Validation
Before setting your automation to run automatically, it is important to verify the connection:
Run Once: Click on your module & enter some dummy data. Right-click on the module and choose the Run this module only option, this will run the module usinf the dummy data you entered.
Sample Data: Ensure that the trigger you are using actually has data to send. For example, if you are pulling drafts from LiGo, make sure at least one draft exists in your account. This helps avoid wasting credits inside Make.
Review Logs: Check the execution log to confirm that the data was mapped correctly and that no errors were returned.
Note: The "Run this module only" will run the module in production. Ex: You choose the "Publish Post to LinkedIn" module & test this module, the module wil create a post in LinkedIn.
Security & Operational Best Practices
To keep your account and data safe, please observe the following:
API Security: Your API key is a sensitive credential. Never share it publicly or include it in screenshots.
Regenerating Keys: If you believe your key has been compromised, regenerate it in your LiGo settings immediately to obtain a new one & to disable the old one.
Descriptive Naming: Give your scenarios clear names (e.g., "ClickUp DM to LiGo Drafts") to make them easier to manage and troubleshoot.
Monitoring: Set up simple alerts or check your Make.com dashboard regularly to ensure your scenarios are running as expected.
Troubleshooting and Support
If your integration fails to perform correctly, follow these steps:
Check the API Key: Ensure the key was copied exactly without any extra spaces.
Rate Limits: Verify that you have not exceeded the task limits on your LiGo or Make.com plans.
Missing Data: If a trigger isn't firing, perform a manual action (like publishing a post) to provide the system with sample data to capture.
Contacting Support
If you cannot resolve an issue, you can contact LiGo support through the message icon located on the bottom right of the screen. To receive a faster diagnosis, please include:
Your account email and plan level.
The name of the scenario and the specific step that failed.
Screenshots of the error message and the execution history.
The sample request and response logs from Make.com.
Frequently Asked Questions
Q: Who can use LiGo with Make.com?
LiGo can be used in Make.com if you have an active paid LiGo subscription. You’ll also need to accept LiGo’s Make.com invite link to enable the integration.
Q: What are all the different automations provided by LiGo in Make.com?
You can automate common LinkedIn content workflows, such as:
Drafting, scheduling, and publishing LinkedIn posts
Repurposing long-form content into LinkedIn-ready posts
Generating post ideas using data from other tools
Syncing posts and drafts with apps like Google Drive, Slack, ClickUp, and Notion
Sending content ideas or drafts into LiGo from external sources like Google Sheets or emails
Q: How can I disconnect my accounts from Make.com?
In Pabbly Connect, select Connections from the sidebar - You will be presented with a list of all your past connections
Select the connection that you would like to update/delete.
You can also click on Verify to ensure that the connection still exists.
You can now update or delete your any of your connected accounts
Q: Why can’t I find LiGo on Make.com's app list?
If you cannot find LiGo in your Make.com app list then you have yet to accpet the invite. If you've accepted the invite and are still unable to find it then please contact support.
Q: Why isn’t my automation running or triggering correctly?
If a scenario isn’t working as expected, check the following:
Make sure your API key is correct and doesn’t include extra spaces
Confirm your trigger has actual data to work with (for example, at least one draft or post)
Review the execution logs in Make.com for mapping or module errors
Verify you haven’t exceeded task or rate limits on either platform
If the issue persists, contact LiGo support and include your scenario name, the failed step, and execution logs for faster help.