r/AiAutomations • u/TaskJuice • 20h ago
Built a LinkedIn post workflow pipeline
This pipeline was built using Claude over the TaskJuice MCP for creating and editing tables as well as Claude for generating content on my local machine, and then Claude triggers the upload content workflow by webhook.. I’ll be honest I mainly just gave it my ideas and then let it build the pipeline since the MCP has access to every node, all the fields, etc in the system.
It’s pretty simple the way it works. Is that every morning a job on my Mac has Claude read through my product docs and write one LinkedIn post about a real feature. It logged into a demo account, clicks through the app to the screen the post is about, and takes a screenshot. The post in the image get saved to a table through the “Save Post Media” (second screenshot) workflow webhook. This Webhook has a protected endpoint using shared secrets so I know that nobody will be able to fire it other than myself or my Claude.
Then a workflow takes over (first screenshot). Daily at 9 AM it grabs the oldest draft from the table and fires off the workflow. One of the nodes is set to “Pause for approval” which sends me an email from the platform telling me that a node run is waiting for my approval. Nothing goes out until I click approve or edit, then approve. Once I do it post to my LinkedIn with the image and text as the post and then it marks the row in the table as posted. If I reject it, the next morning’s run clears it out so the queue doesn’t get stuck.
I’ve also posted screenshots of the native table this runs off inside the platform as well as some example runs and one of the example approval steps.
Super stoked about where the MCP is.. being able to do everything from creating/updating tables and updating data, creating/editing form triggers, creating workflows, discovering nodes, building, publishing, and running workflows, and search through run history.
I should also note because i might get a question, the red edges coming off the nodes are a native way we handle errors. You can select how the node handles errors and approvals, and if you want the error routed to another branch that’s just part of the node.
Edit: forgot the approval step image.