The workflow
At /marketing/social/accounts. Each network is authorised individually against your own account.
The social agents repurpose long-form content into posts; you can also write directly.
Posts sit in a queue with their target network and time.
The same review discipline as any other run.
Queue
11 queued · 3 accounts connected
From the March article
Repurposed from /help/lead-times
A note on where this came from
Social used to be a module of its own in the rail. Its publishing moved here, and rather than leaving a greyed-out icon behind, the old module was removed from the suite entirely. A module nobody can reach is noise in the rail and a support question waiting to happen — so if you remember a Social icon and cannot find it, this is where it went.
What this does not do
Publishing only. Replies and mentions are not brought back in.
Performance is read through the analytics agents and your own network tools.
Media is attached, not produced.
What can be published depends on what each network's API permits.
Questions
Can we schedule far ahead?
Yes, the queue takes dates.
What happens if a connection expires?
The queued post fails and is shown as failed rather than dropped.
Can two brands share a queue?
Use separate workspaces.
Related
Every agent execution in erp.io Marketing is a run: its input, output, cost and state — and the review step that stands between a run and publication.
IntegrationsConnecting analytics, ad and social accounts to erp.io Marketing, what the agents can see through them, and what happens when a connection expires.