Change many posts at once
postfjord_bulk_update_postsApply one change to up to 200 posts at once: reschedule, draft, cancel, or delete, with a result for each post.
Instructions
Use when the same change applies to many posts (move a week, unschedule, cancel, delete); for one post use postfjord_update_post or postfjord_schedule_post. One action on up to 200 posts, with a result per post. reschedule moves scheduled posts, and drafts that have a date, by shift ({ days, hours, minutes }, negative moves them earlier) or so the earliest starts at startAt and the others keep their spacing; it needs a key that may publish and is refused while the workspace is paused. draft takes scheduled or cancelled posts out of the queue as drafts that keep their date. cancel cancels scheduled posts. delete removes drafts, cancelled, failed and scheduled posts for good (a key with only the Drafts level deletes drafts and cancelled posts), so tell the person how many and get a yes first. Posts being published or already published are never changed: they come back as skipped with a code, like not_found, publishing, published, key_scope, past, month_full, x_addon or changed. On a retry after a timeout or error, send the same idempotency_key: the first answer comes back and nothing is made or sent twice.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| shift | No | For reschedule: how far to move each post. Days keep the time of day in the workspace time zone. At most 366 days. | |
| action | Yes | ||
| postIds | Yes | Post ids from postfjord_list_calendar, at most 200. | |
| startAt | No | For reschedule, instead of shift: an ISO 8601 date-time with time zone for the earliest post, e.g. 2026-11-02T09:00:00-05:00. | |
| idempotency_key | No | Your own id for this one action, for example post-20261006-launch. Make a new one for each new thing; send the same one again only when you retry. Left out, the exact same call within 10 minutes counts as a retry. |