01
Auto-post from RSS
Connect any blog or news RSS feed. Every time a new item is published, Make creates a scheduled post in ContentStudio using the title, link, or description you map from the feed.
Make IntegrationAutomate social media with the ContentStudio Make integration
Connect ContentStudio to Make and turn actions across your favorite apps into scheduled social posts. Build your workflow once, map the fields you need, and let Make automatically create and schedule posts in ContentStudio without manual copy and paste.
Publishes to:
X / Twitter, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Google Business, Threads, Bluesky, Tumblr, and more.
Quick ReferenceCore CapabilitiesSetupVideo WalkthroughUsing the integrationSecurity & TrustTroubleshootingFAQs
Quick Reference
Everything you need to get started
- App name
- ContentStudio (search "ContentStudio" in Make)
- Actions
- Create Social Post, Delete Post, Make an API Call
- Triggers
- List Workspaces, List Social Accounts, List Posts
- Auth method
- API key (Settings → API in ContentStudio)
- Rate limit
- 60 requests per minute (3,600 per hour)
- Required fields
- Workspace ID, Social Accounts, Post caption
- Requirements
- An active ContentStudio API key
Core Capabilities
What you can automate with the Make integration
Use Make to connect the apps you already use with ContentStudio and automate social posting. Create your scenario, map the fields, and let each new event trigger a scheduled post. ContentStudio integrations make workflows like this easier to set up.
02
Create Social Post
The core action. Make creates and schedules a new post in your selected workspace and accounts, with caption, images, video, schedule time, and first comment pulled from your trigger app.
03
Delete Post
Remove an existing post from ContentStudio through a scenario. Pair it with any trigger so scheduled or published posts can be cleaned up automatically as part of a wider workflow.
04
Make an API call
Go beyond the pre-built modules. Call any ContentStudio API endpoint directly from your scenario, giving you the flexibility to build advanced workflows the standard actions do not cover.
05
Read your workspaces and accounts
Use List Workspaces and List Social Accounts to pull the workspace and account IDs your scenario needs, so it always posts to the right place before it creates content.
06
Read your posts
The List Posts search returns the posts available in a workspace and can filter by status, so downstream modules can act on what is already scheduled or published.
Setup
Get started in five steps
Make runs on a visual canvas, so building the connection is a matter of dropping in modules and linking them. Five steps take you live.
1
Step 1 - Get your ContentStudio API key
Open ContentStudio, head to Settings → API, and generate your key. This is the credential Make uses to post on your behalf, so keep it somewhere private.
2
Step 2 - Start a scenario and pick a trigger
In Make, click Create scenario for a blank canvas. Add your first module as the trigger, for example RSS with Retrieve RSS feed items, then paste your feed URL so Make knows what to watch.
3
Step 3 - Add ContentStudio and connect it
Click the plus to add an action module, search ContentStudio, and pick Create Social Post. Choose Create a new connection, drop in your API key, and Make links your account in one popup.
4
Step 4 - Map the trigger data into your post
This is where the canvas earns its keep: instead of typing content, you pull fields from the previous module. Set the Workspace and Social Accounts, then map the caption from your RSS title or description.
5
Step 5 - Run once, then activate
Use Run once to fire the scenario with real data and confirm the post lands in ContentStudio. If the caption, media, and timing look right, toggle the scenario on and it runs on every trigger from there.
Video Walkthrough
Build your first scenario in a few minutes
Prefer to watch first? This walkthrough builds a working scenario from scratch, connecting a trigger to ContentStudio's Create Social Post action and scheduling the post live, so you can follow along before you start.
Using the integration
See the Make workflows in action
These are real automation patterns teams use to save hours of manual posting. Set the trigger once, map the fields, and the posting happens on its own.
The RSS feed autopilot
→ A new blog post publishes in your RSS feed.
✓ Make creates a scheduled ContentStudio post across your accounts, using the title and excerpt you mapped.
The AI content summarizer
→ Your blog publishes a long article.
✓ Make sends it to an AI tool for a short summary, then schedules that summary as a post in ContentStudio.
The collaboration workflow
→ A teammate adds a row to your content planning Google Sheet.
✓ That row becomes a scheduled post in ContentStudio, so one person handles the actual scheduling.
The event promotion cascade
→ A new event is added in Google Calendar or Airtable.
✓ Make triggers for promotional posts in ContentStudio, so reminders and last-chance posts run on schedule.
Security & Trust
Automation you can watch and control
Make gives you a visible record of every run, a test mode before anything goes live, and a scoped key you can revoke at will, so nothing posts without your say-so.
✓
A key you can revoke: Your connection runs on a single ContentStudio API key that reaches only your account. Deactivate it in settings anytime to cut Make off instantly.
✓
One connection per account: Give each its own key and its own Make connection. Scenarios then stay pinned to the right workspace, with no risk of content crossing accounts.
✓
See every run in the log: Make keeps a full history of each scenario execution. If something posts wrong or stops firing, open the log to see exactly what ran, when, and with what data.
✓
Nothing posts untested: Run once sends a real post through before you switch the scenario on. Check how it landed in ContentStudio first, so a bad caption or missing image never reaches your audience.
Troubleshooting
Quick fixes for common problems
Most issues come down to the API key, the field format, or the trigger firing more than once. Here are the common ones and how to fix them.
"API key invalid" error
Your key expired or was deactivated. Generate a new one in ContentStudio settings and reconnect your Make connection.
Posts not appearing in ContentStudio
Check your Make dashboard to confirm the scenario ran, verify you selected the right workspace and accounts, and remember scheduled posts appear in the Calendar, not published posts.
Images not loading
The image URL must be publicly accessible. If it lives on Dropbox or Google Drive, set sharing to "anyone with the link," or host the image on your own site.
Scenarios firing too often
A scenario can trigger repeatedly when the trigger is too broad. Add filters to narrow when it fires, or adjust the trigger type so it runs only when you want it to.
Wrong posting time
Use the format YYYY-MM-DD HH:mm:ss in 24-hour time, and remember ContentStudio uses your workspace timezone when scheduling.
Duplicate posts
You likely have more than one scenario doing similar work, or a trigger firing twice. Check your Make dashboard and turn off or adjust the duplicates.
FAQs
FAQs
What is the ContentStudio Make integration?+
The ContentStudio Make integration connects ContentStudio to the other apps you use, so events like a new RSS item or form entry automatically create and schedule social posts. It runs on Make's visual scenario builder, with no code required.
How do I set up the ContentStudio Make integration?+
Get your API key from ContentStudio settings, create a scenario with a trigger app, add ContentStudio with the Create Social Post action, paste your key, map the required fields, then test and run.
Where do I get my ContentStudio API key?+
Generate it from ContentStudio settings under Settings → API. Full steps are covered in the ContentStudio API guide.
Can I connect multiple ContentStudio accounts in Make?+
Yes. Each account needs its own API key and its own separate connection in Make.
What happens if my API key is deactivated?+
You will need to generate a new API key in ContentStudio and reconnect it in Make.
Which actions can I automate with ContentStudio in Make?+
Three actions: Create Social Post to publish posts, Delete Post to remove a post, and Make an API Call to send custom requests to ContentStudio's API for advanced use cases.
What can trigger a post through the ContentStudio Make integration?+
Almost any app can be the trigger, since ContentStudio is the action. Common ones include a new RSS feed item, a new Google Sheet row, a form entry, or a saved article in a curation app.
Is there a rate limit?+
Yes. You can make 60 requests per minute, which is 3,600 requests per hour. Each module in a scenario counts as one request.
Do I have to type the caption manually?+
No. Map a field from your trigger app, such as the RSS title or description, so the caption fills in automatically.