Automation workflows
Build a complete read, change, review and publish workflow with revision checks, bounded retries and verifiable public results.
Last reviewed 15 October 2026Automations operate on one token-bound workspace and share the dashboard's permissions and plan limits. Begin with a read, preserve the returned revision and verify the effect of every write before scheduling unattended work.
Read identity, capabilities and current state
Use https://orbitpage.com/api/v1 as the REST base and send Authorization: Bearer with a personal token. Read the workspace and intended resource before writing. Confirm the returned identity, required scopes and current revision; use the generated reference for the operation's schema and available capabilities.
Change with a revision precondition
Send If-Match for operations that require the revision you just read. A missing precondition returns 428. If 409 reports revision_conflict, fetch the latest resource, review competing changes and reapply the intent. Other 409 responses can describe business conditions and should not be blindly retried.
Validate a replacement collection before sending it: a full replacement can remove entries you omit. Use a supported field-level patch when that matches your task. Keep a backup before bulk changes.
Review drafts and verify publication
Supported profile, theme, page and settings writes save a draft by default; the documented publish option or POST /publication publishes eligible changes. Link PUT/PATCH operations publish immediately. Read each endpoint's effect instead of assuming that every write behaves alike.
When batching draft changes, carry forward the new revision returned by each operation. Publish the reviewed revision, inspect publication status and open the public page. Restoring through MCP creates a private draft and requires a separate reviewed publication.
Handle failures without duplicate actions
Check token expiry or revocation for 401, and scopes, membership and plan for 403. Honor Retry-After on 429. After a timeout, read current state before repeating an operation that sends, publishes, deletes or bills. A failed network response does not prove the server did nothing.
Use pagination and limits documented for the specific endpoint. Log timestamps, operation names and sanitized error codes, never bearer tokens or signed customer URLs. Revoke retired credentials and test recovery before enabling an unattended schedule.