Google Sheets to LinkedIn with Make
Each new row in a Google Sheet schedules a LinkedIn post through the bundle.social API.
Work in progress
Make integration for social media publishing
Post to 15 social networks from your Make scenarios. We are building a native bundle.social app for Make. Until it ships, the HTTP module calls the same API with a few fields.
Last updated
Make HTTP module: request content for POST /api/v1/post/
{ "teamId": "team_123", "title": "Launch update", "postDate": "2026-11-12T09:00:00.000Z", "status": "SCHEDULED", "socialAccountTypes": ["LINKEDIN"], "data": { "LINKEDIN": { "text": "We just shipped a new feature." } }}The native Make app is in progress
We are building bundle.social modules for Make, with a connection screen, team dropdowns, and per-platform post fields. There is no release date yet. Join the list below and we will email you when it is ready.
Connect Make with the HTTP module
Scenarios built this way keep working after the native app ships.
HTTP module
One module per API call. Map fields from earlier modules into the JSON body.
- 01
Create an API key
In bundle.social > Organization > API Keys, create a key and copy it. - 02
Find your team ID
Add an HTTP module with GET https://api.bundle.social/api/v1/team/ and the x-api-key header, run it once, and copy the id of the team you want to post from. - 03
Add the post request
Add HTTP > Make a request. Set the URL to https://api.bundle.social/api/v1/post/, the method to POST, add the x-api-key header, and choose Raw with JSON as the body. - 04
Write the body
Paste the post body and map your fields into it. Each platform insocialAccountTypesneeds an entry under data with its text and, for media, itsuploadIds. Turn on Parse response so later modules can use the post id and status.
What the HTTP module can reach
The HTTP module reaches every endpoint of the public API. These are the calls most scenarios need.
| Call | What it does |
|---|---|
POST /api/v1/post/ | Create a post, scheduled or published right away. |
POST /api/v1/upload/from-url | Add an image or video from a public URL and get an upload id for the post. |
GET /api/v1/post/{id} | Read a post back to check its status and permalink. |
GET /api/v1/analytics/post | Read likes, comments, shares, and views for a post. |
GET /api/v1/team/ | List teams and the social accounts connected to them. |
A Make recipe to start from
Each template has its own page with setup steps and requirements. See all Make templates.
Get an email when the Make app is ready
Leave your email and tell us which scenario you want to build. We use the answers to decide what the app covers first.
Troubleshooting
| Problem | Fix |
|---|---|
| 401 or 403 from the API | Check that the header name is exactly x-api-key and that the key has not been deleted. Analytics calls return 403 on the Free plan. |
| Validation error in the response | The API names each invalid field, for example data.LINKEDIN.text: Required. Every platform in socialAccountTypes needs an entry under data. |
| Later modules cannot see the post id | Turn on Parse response in the HTTP module, then run the scenario once so Make learns the output. |
FAQ
Is there a bundle.social app in Make?
Not yet. The native app is in progress. Until it ships, the HTTP module covers the whole API with your API key.
Will my HTTP scenarios break when the app ships?
No. The app will call the same API, so scenarios built on the HTTP module keep working.
Can I upload media from Make?
Yes. Send the file URL to POST
/api/v1/upload/from-url, then put the returned id in uploadIds of the post.Build your first Make scenario
Create a free account, copy an API key, and add one HTTP module.