Nuelink
Social MediaConnect AI agents to Nuelink, a social media scheduling and publishing platform. Agents upload media and schedule posts into a collection, which distributes them to every channel in it.
What This Integration Enables
Most social schedulers ask you to pick channels. Nuelink asks you to pick a collection, and the collection decides which channels. That is not a cosmetic difference, and understanding it is most of what it takes to build well here. The object model runs account, then brands, then collections, then channels. A brand is a workspace with its own timezone. A collection is a named group of connected channels. A post is created inside a collection and distributed to every channel in it. Which means the question a flow has to answer correctly is never "which accounts should this reach" but "which collection describes the audience I mean", and the answer to the second question is maintained by people in the Nuelink interface, not by the flow.
That is a reasonable design for anyone running more than one brand, which is who this connector is for. Agencies, franchise groups, and multi-property operators spend most of their scheduling effort on the bookkeeping of who goes where, and Nuelink turns that bookkeeping into a first class object you configure once. The connector reads it faithfully. List Brands returns each brand with the timezone that governs how scheduled times are interpreted. List Collections returns the collections in a brand with their status and the channels attached to each one. List Channels returns the connected accounts across Instagram, X, Facebook, LinkedIn, TikTok, YouTube, Pinterest, and Threads with each channel's platform type and connection status. Get Profile is the health check that confirms the key is live.
Be precise about one thing that the surface description elsewhere gets loose about: this connector does not create or edit collections. There is no action here that adds a channel to a collection, removes one, or makes a new collection. List Collections is read-only, and its id is a required input to Create Post. Collections are organized in Nuelink; flows consume them. The two write actions are Upload Media, which pulls a file from a public URL into a brand's media library and hands back an opaque id, and Create Post, which is where everything happens. Create Post supports four publish modes: adding to the brand's queue, scheduling for an exact time, publishing immediately, or saving as a draft. It optionally attaches media by uploaded id or by direct public URL, a poll, an auto-comment, a story flag, and per-platform overrides. Note that Nuelink's public API is an alpha release, so endpoint and response shapes may still move, and that scheduled times use the brand's timezone rather than UTC, which is the single most common source of a post landing at the wrong hour.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A calendar that publishes itself, per brand
An agency keeps its editorial calendar in Google Sheets, one row per post with a brand, a collection name, a caption, an asset URL, and a publish time. A scheduled flow reads the rows due in the next window. For each one it calls List Brands to resolve the brand and read its timezone, then List Collections to resolve the collection name to an id, calls Upload Media with the asset URL to get a media id, and calls Create Post in Schedule for Later mode with the time formatted for that brand's timezone. The post reaches every channel in the collection with one call. Where a platform needs something specific, the per-platform overrides carry it: a YouTube playlist, TikTok inbox delivery, an Instagram Collab. The row is written back with the result so the calendar and the scheduler stay in agreement rather than diverging quietly.
Generated assets that go out with their captions
A campaign flow produces an image and a caption, then needs both in front of an audience without a person copying files between tabs. The agent calls Upload Media with the public URL of the generated asset, which downloads it into the brand's media library and returns an id, then Create Post referencing that id along with the caption. Supported types are PNG, JPG and JPEG, MP4, MOV, and PDF up to 100 MB, and a media item takes either an uploaded id or a direct public URL but never both. Where the post is a question rather than an announcement, the flow attaches a poll instead of a caption, which LinkedIn, X, Telegram, Threads, Mastodon, and Bluesky honor and other platforms ignore, so the collection membership determines whether the poll is a feature or a no-op. The agent checks List Channels first and reports which channels in the collection will silently drop it.
A standing answer to "what is connected right now"
Connections expire. A token gets revoked, a client changes an account password, a platform forces a reauthorization, and the first anyone notices is a week of posts that went nowhere. A daily flow walks List Brands, then List Channels per brand, and reports any channel whose connection status is not healthy to the account owner in Slack, naming the brand, the channel, and the platform. The same pass records the current membership of each collection from List Collections, so when a client asks why a post did not appear on LinkedIn the answer is a dated record rather than a reconstruction. This costs nothing to run and turns a class of silent failure into something somebody sees on the day it happens.
Human-in-Loop Highlight
Create Post has four publish modes, and one of them has no way back. Add to Queue, Schedule for Later, and Save as Draft all leave a window in which a person can intervene in the Nuelink interface. Publish Immediately does not, and this connector ships no delete, no update, and no retraction action of any kind. Once a post publishes, nothing in this surface can pull it back from Instagram, X, LinkedIn, TikTok, or anywhere else the collection reaches. What compounds that is where the blast radius is defined: it is the collection's membership, and the collection is edited by people in Nuelink, not by the flow. The agent can read the current membership with List Collections and List Channels, but it cannot know whether someone added the client's corporate LinkedIn to a collection that used to hold only two Instagram accounts. A caption written for a casual audience reaching a formal one is the kind of mistake that is obvious to a human in one glance and invisible to a flow. So the agent enumerates rather than assumes. Before any Create Post call in Publish Immediately mode, it calls List Collections and List Channels, and puts the resolved list in front of the account owner: "Publishing now to collection Spring Launch on brand Northside. That collection currently holds 5 channels: Instagram @northside, TikTok @northsideco, LinkedIn Northside Group corporate page, X @northside, Threads @northside. Caption is 240 characters, one image attached. Publish, or save as draft?" For scheduled and queued posts, which retain an intervention window, the agent proceeds on its own. Putting a human-in-the-loop gate on exactly the mode that cannot be undone is what makes it reasonable to let a flow publish for a dozen client brands without a person in every single one.
Agent Capabilities
6 actionsAccount and Structure
4- Get Profile Returns the authenticated Nuelink user's profile, including id, display name, account creation date, and IANA timezone. The cheapest way for a flow to confirm the API key is valid before doing anything that matters.
- List Brands Lists the brands, meaning workspaces, in the connected account, paginated. Each brand exposes its own timezone, which governs how scheduled post times are interpreted, so read it rather than assuming UTC. A brand id is the brandId path parameter for the other operations.
- List Collections Lists the collections in a brand, paginated. A collection groups the connected channels a post is distributed to, so its id is required to create a post, and each collection reports its status and the channels attached to it. This action reads collections; it does not create or modify them.
- List Channels Lists the social channels connected to a brand, covering Instagram, X, Facebook, LinkedIn, TikTok, YouTube, Pinterest, and Threads, with each channel's platform type and connection status. Paginated. Use it to catch expired connections before they cost a week of silent failures.
Publishing
2- Upload Media Downloads a file from a public URL into a brand's media library and returns an opaque media id to reference when creating a post. Accepts a single image in PNG, JPG or JPEG, a video in MP4 or MOV, or a PDF, up to 100 MB. You can skip this entirely and pass a direct public URL in Create Post's media field instead.
- Create Post Creates a post in a collection and distributes it to every channel in that collection, subject to the publish mode. Supports queueing to the brand's queue, scheduling for an exact time, publishing immediately, or saving as a draft. Optionally attaches media by uploaded id or direct URL, a poll, an auto-comment, a story flag, and per-platform overrides. Scheduled times are read in the brand's timezone, and a caption of 1 to 3000 characters is required unless a poll is supplied.
Frequently Asked Questions
What can FlowRunner do with Nuelink?
FlowRunner agents can run Get Profile, List Brands, and List Collections in Nuelink, plus 3 more actions.
Does connecting Nuelink to FlowRunner require OAuth?
No. Nuelink connects to FlowRunner with an API key, no OAuth flow required.
Can Nuelink trigger a FlowRunner workflow automatically?
Nuelink doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Nuelink
$100 in credits. No card required. Connect in minutes.