Use Lockers
Post drafts from another tool
Let a connected tool draft posts for your team to review, with publishing kept as a separate permission.
The short version
- A connection with Write post drafts can create and update drafts in your community, and every draft it makes stays attributed to that connection.
- Drafts sit in the community's drafts for your staff to read. Nothing reaches members until a person acts, or until you grant Publish posts on purpose.
- If someone edits a draft inside Lockers after the tool last read it, the tool's next change is refused until it reads the draft again.
Before you start
Your Locker needs an active Pro plan, and you need to be an owner or admin. Drafts travel over a customer API key, so either use a connection you already have or create one at Admin, then Settings, then Integrations. The article Connect another tool to your Locker covers the key itself.
Two permissions do the work. Read post drafts is described as Read integration-created drafts. Write post drafts is described as Create and update attributed drafts. The Content drafts preset grants both and states its own limit: publishing is not included.
Set the permissions on the key
A course restriction on the key does not narrow drafts. Restrictions apply to course, enrollment, and completion access only, so a key limited to two courses can still draft about anything. See Choose API permissions for the rest of the list.
- 1
Open Integrations
Open Admin, then Settings, then Integrations, and find the form under Customer API keys.
- 2
Name the connection
Enter a Connection name you will recognize later, such as the name of the tool writing the drafts.
- 3
Grant the two draft permissions
Choose the Content drafts preset, or choose Custom and tick Read post drafts and Write post drafts yourself.
- 4
Create and store the key
Select Create key, copy the key once while it is on screen, and store it in a secret manager or an environment variable.
- 5
Check it
Use Test the connection to confirm the permissions came through as you set them.
What the tool can do
The connection can create drafts, update them, and delete them. Each one carries the connection's identity, so your staff can see which tool wrote what when several are running at once. That identity survives a key rotation, which means last month's drafts stay attributed to the same connection after you issue a fresh key for it.
Drafts land in the community's drafts, the same place your team already looks. Reviewing and editing happen there, by a person, exactly as they do for a draft someone typed by hand.
Publishing stays a decision
Publish posts is a separate permission, described as Publish a draft as a separate action. Leave it off and the tool can fill your drafts area all day without a single post going out. Turn it on when the source is one you trust without a read, and the volume makes checking every item impractical.
Keeping the two apart is why an automated feed is worth running at all: a misconfigured filter on the other end produces drafts you delete, rather than posts your members already saw.
When a change is refused
Updates and publication use a version check. If a member of your staff opened the draft in Lockers and changed it after the integration last read it, the integration's change is turned down until it rereads the draft and works from the current text.
That rule exists so a scheduled sync cannot quietly overwrite an editor's work. Most tools handle it by reading again and reapplying their change. If a connection keeps failing on the same draft, look at whether someone is editing it in Lockers at the same time the tool runs.
Webhook events for drafts
Outbound webhooks carry Post draft created, Post draft updated, Post draft deleted, and Post published. Post events require the endpoint to be bound to a named API connection, so pick the connection in the Named API connection field when you add the endpoint. The article Receive webhooks from your Locker has the setup and the retry behavior.
For whoever builds the connection
The contract lives at lockers.social/api/openapi.json, with a Postman collection at lockers.social/api/lockers-customer-api.postman_collection.json and a Node client example at lockers.social/api/examples/client.mjs. Send those to the developer or paste them into the no-code tool that is doing the writing.
Build the smallest useful version of your community.
Start with a feed, classroom, calendar, messages, and member list. No card required.
Start a community