content_publications_remind

Tool

content_publications_remind

Send the publish reminder AGAIN.

Send the publish reminder AGAIN. Repeat reminders are never automatic: the system cannot double-publish, but a person can, so a second nudge only ever happens because someone asked for it.

Behavior

HTTP: POST /content/publications/:id/remind

Arguments

Name	Type	Required	Description
id	string	•	The publication id returned by content_publications_schedule.

Response

Field	Type	Always	Description
id	string	•	Publication id.
text	string	•	The exact text that will be published to this channel — markdown already flattened to plain network text at schedule time. Not the markdown source; that stays on the post.
state	string	•	pending (queued) -> publishing (the reminder was sent; a person is publishing by hand) -> published (confirmed) \| failed \| cancelled.
postId	string	•	The post being published.
costUsd	number	•	What publishing this costs in USD, computed when it was scheduled. On X a post carrying a link costs 13x a plain one. Null means the cost is not known — an auto channel refuses to dispatch it.
attempts	integer	•	How many dispatch attempts have been made.
channelId	string	•	The channel it is published to.
costBasis	string	•	Which rate produced costUsd: "plain", "link" or "free".
createdAt	string	•	ISO-8601 creation time.
lastError	string	•	The most recent failure, if any.
updatedAt	string	•	ISO-8601 time of the last change.
externalId	string	•	The network's id for the published post, once known.
externalUrl	string	•	URL of the published post, once known.
publishedAt	string	•	ISO-8601 time it was confirmed published.
scheduledAt	string	•	ISO-8601 time the publication is due.
reminderCount	integer	•	How many reminders have been sent for this publication.
idempotencyKey	string	•	The key that makes a retry the same publication.
reminderSentAt	string	•	ISO-8601 time the most recent reminder went out, or null if none has.

Try it

Send the publish reminder AGAIN.

When to use

Send the publish reminder AGAIN. Repeat reminders are never automatic: the system cannot double-publish, but a person can, so a second nudge only ever happens because someone asked for it.

Example

Ask your agent something like this:

Send the publish reminder AGAIN.

The agent will invoke content_publications_remind with these arguments:

{
  "id": "<id>"
}