DotSimple
Social MediaConnect AI agents to DotSimple, a social media content planning and publishing tool. Agents upload media, schedule posts across connected accounts, and organize them with tags.
What This Integration Enables
DotSimple is scoped to a workspace, and that single design decision is why this connector suits agencies and multi-brand teams rather than a single account holder. The Access Token and the Workspace UUID are both required, and the workspace UUID sits in the API path itself, so every call names the client it belongs to. There is no ambient current workspace to get wrong halfway through a run. Inside that boundary, List Accounts and Get Account report the connected networks, Upload Media File loads assets by public URL into the library, and Create Post assembles a post through a versions array where each version carries content blocks and provider-specific options. Schedule Post, Add Post To Queue, and Update Post move that post along. Tags are the organizing layer: List Tags, Get Tag, Create Tag, and Delete Tag manage them, and Create Post and Update Post attach them to posts through a Tag IDs array.
Be clear about where tags stop being useful, because the temptation is to treat them as a reporting layer. They are not. DotSimple's API exposes no analytics or performance actions at all, so tags group and filter posts inside DotSimple, and any performance question has to be answered from the networks themselves or from a warehouse the flow writes to. Design accordingly: if a client needs a monthly performance report, tag posts here for calendar hygiene and push the identifiers into Google Sheets or a database where the numbers actually live. The other structural fact is that this connector ships no triggers, because DotSimple publishes no event subscription. Nothing here listens for a published post or a failed send. A flow starts from a schedule or from an approval elsewhere, and List Posts is polled to learn what happened, since the response carries each post's status, target accounts, tags, and scheduling timestamps.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A month drafted by a flow and released by a person
A client's content plan is approved in Airtable at the end of each month. A flow reads the approved rows, calls Upload Media File for each asset URL, and holds the returned numeric media ids. For every row it calls Create Post with the target account uuids, the versions array carrying the body text and media ids, and the Tag IDs for the campaign, deliberately omitting the scheduling flags so each post lands as a draft. It then calls List Posts, compares the draft count and tag distribution against the approved plan, and sends the account manager a summary. Nothing is scheduled yet. The flow built the month; the person commits it.
Reactive posting that stays inside the client's queue
A retail client wants to react to stock movements without breaking the rhythm of the planned calendar. When an item sells through in Shopify, an agent calls Upload Media File with the product image, calls Create Post targeting the two networks that carry product content, and then calls Add Post To Queue rather than publishing immediately. The post enters the workspace queue and goes out in the next open slot alongside the planned content. Reactive content lands in the client's actual cadence instead of arriving as an unscheduled interruption on a Tuesday afternoon.
Library hygiene without guessing what is still in use
Media libraries grow until somebody deletes the wrong file. A quarterly flow calls List Media Files across the workspace and calls List Posts with pagination to build the set of media ids still referenced by drafts, scheduled posts, and published posts. The difference is the genuinely unreferenced set. The agent posts that list to the account manager in Slack with file names and sizes rather than calling Delete Media Files on its own, because a media id that no current post references may still be the only copy of an asset a client paid for. Cleanup is proposed by the flow and confirmed by a person.
Human-in-Loop Highlight
The dangerous call in this connector is not the one that publishes. It is Delete Multiple Posts, which takes an array of UUIDs and removes all of them in a single request. A month of drafted and scheduled posts is future work that nobody has seen the results of yet, and DotSimple offers no analytics surface to reconstruct what was there. The Access Token is scoped to one workspace, which means one client, so a batch assembled from a slightly wrong filter erases a specific client's calendar rather than a shared one. So whenever a cleanup flow reaches this action, the agent stops. It calls List Posts and Get Post to resolve every uuid in the batch into something a person can actually judge, then sends the account manager the resolved list: "Cleanup would delete 34 posts in the Northwind workspace: 6 published, 28 scheduled between the 9th and the 30th, tagged Spring Launch. Delete Multiple Posts cannot be undone and there is no analytics record of the scheduled ones. Proceed, or drop the scheduled posts from the batch?" The agent is allowed to build a client's month unattended. It is not allowed to erase one on a filter's say-so.
Agent Capabilities
18 actionsAccounts
2- List Accounts Lists all connected social media accounts in the workspace. Run it before building a calendar so a disconnected network surfaces as a check rather than as a batch of posts targeting an account that can no longer publish.
- Get Account Retrieves a single connected account by UUID. Used when a flow needs to confirm the network and status of one specific target before scheduling against it.
Tags
4- List Tags Lists all tags in the workspace. Used to resolve campaign names into the numeric ids that Create Post and Update Post expect.
- Get Tag Retrieves a single tag by UUID. Used for verification when a flow is matching a campaign name to an existing tag rather than creating a duplicate.
- Create Tag Creates a tag with a name and hex color. Used at campaign kickoff so every post created afterwards can carry the campaign's grouping from the moment it exists.
- Delete Tag Deletes a tag by UUID. Deleting a tag removes the grouping from every post that carried it, and since DotSimple exposes no analytics, that grouping cannot be reconstructed from performance data afterwards.
Media
4- List Media Files Lists media files in the library with pagination. The first half of any library audit, and the way a flow discovers what assets a workspace already holds before uploading a duplicate.
- Get Media File Retrieves a single media file by UUID. Used to confirm an asset exists and resolve its details before attaching it to a post.
- Upload Media File Uploads an image or video from a public URL into the workspace media library. Returns the numeric id that posts use to attach media, so this always runs before the Create Post that references it.
- Delete Media Files Deletes one or more media files by their numeric ids. Batch destructive, and an asset that no current post references may still be the only copy the client has.
Posts
8- List Posts Lists posts in the workspace including drafts, scheduled, and published, with pagination. Each post returns its status, target accounts, content versions, attached tags, and scheduling timestamps, which makes this the polling action that stands in for the triggers DotSimple does not offer.
- Get Post Retrieves a single post by UUID. Used to resolve a uuid into something a person can read before any action is taken against it.
- Create Post Creates a post targeting one or more connected accounts. Content is supplied through the versions array, where each version carries content blocks with body text and media ids plus optional provider-specific options. Set a date, time, and timezone to schedule it, schedule_now to publish immediately, or queue to add it to the queue. Omit the scheduling flags and it stays a draft, which is the safe default for anything a person still needs to see.
- Update Post Updates an existing post's accounts, content, tags, or schedule. Used for the revision pass after a review, so approved changes reach the calendar without the post being rebuilt.
- Schedule Post Publishes a post now or schedules it for its set time. This is the action that turns a reviewed draft into a commitment, which is why it is the natural place to put a release gate.
- Add Post To Queue Adds a post to the workspace posting queue. Use it when the right answer is the next available slot in the client's established cadence rather than a specific timestamp.
- Delete Post Deletes a single post by UUID. Used for targeted removal of one item rather than a batch.
- Delete Multiple Posts Deletes multiple posts by an array of UUIDs in one call. The widest destructive action here, capable of removing an entire scheduled month for one client in a single request.
Frequently Asked Questions
What can FlowRunner do with DotSimple?
FlowRunner agents can run List Accounts, Get Account, and List Tags in DotSimple, plus 15 more actions.
Does connecting DotSimple to FlowRunner require OAuth?
No. DotSimple connects to FlowRunner with an API key, no OAuth flow required.
Can DotSimple trigger a FlowRunner workflow automatically?
DotSimple doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DotSimple
$100 in credits. No card required. Connect in minutes.