Automation workflows

Automation access is included in Starter, Growth and Pro. In PB, open your avatar menu and choose Developer API keys. Create a separate key for each connection. Include sites so the connection can select your websites, then grant only the action permissions you need.

Store the key in the platform's connection or encrypted credential store. The PB API base address is https://api.prerenderbuddy.com/v1/developer. Requests use Authorization: Bearer YOUR_PB_KEY.

Use an HTTP Request node with a Header Auth credential: header name Authorization, value Bearer YOUR_PB_KEY. Start with GET https://api.prerenderbuddy.com/v1/developer/sites and select the returned website ID. Add further HTTP Request nodes for the endpoints below. A Schedule Trigger can run evidence checks on your own schedule.

Use an authenticated API request step to call the PB endpoints below. Keep the key in the step's protected authentication configuration. Start with GET /sites to get the website ID. When an article task is still processing, use a delay based on pollAfterSeconds before requesting its status again. Use an approval step before generation or publication.

Use HTTP's authenticated request module with a stored API-key connection. Configure the Authorization header as Bearer YOUR_PB_KEY, choose the method and enter the complete PB endpoint address. Start with GET /sites, then map its website ID into subsequent modules. Keep testing scenarios on demand until you have reviewed the results.

Use an authenticated HTTP action to call the PB endpoints below. Store the Developer API key as a connection secret. Add a schedule trigger for evidence reports, and an approval step before actions that generate or publish an article.

Use the website ID returned by GET /sites in these endpoints. The responses contain recorded workspace evidence; they do not start new AI tracking collections.

1. List article ideas and keep the returned tracked question ID.
2. Prepare a proposal with POST /sites/{siteId}/content/proposals. Send promptId and a new UUID as requestId. Reuse that UUID when retrying the same request.
3. Read GET /sites/{siteId}/content/tasks/{taskId}. Follow pollAfterSeconds while the proposal is processing, then review the proposal and remaining allowance.
4. After approval, call POST /sites/{siteId}/content/tasks/{taskId}/generate with confirmGeneration: true. Generation uses one article from the shared workspace allowance. Repeating the same task does not use another article.
5. Poll the task, then read GET /sites/{siteId}/content/drafts/{draftId}. Review the article text and retain its exact reviewHash.
6. Approve that version with POST /sites/{siteId}/content/drafts/{draftId}/approve, sending reviewHash and confirmReview: true.
7. Deliver through POST /sites/{siteId}/content/drafts/{draftId}/deliver. Send reviewHash and requestedStatus: "draft" to send a CMS draft. Live publication requires requestedStatus: "publish" and confirmPublish: true.
8. To schedule publication, use PUT /sites/{siteId}/content/drafts/{draftId}/schedule with reviewHash, an ISO date including its timezone offset as scheduledFor, an IANA timezone and confirmSchedule: true. Set scheduledFor: null to cancel.

Publishing uses the website's configured destination. A Git release merges the content pull request; your website host still needs to deploy it. If an article changes after review, read and approve the new version. Revoking the key also stops publications scheduled using that key.

See the Developer API reference for response formats and errors. Contact support@prerenderbuddy.com with the platform name, action and error message. Keep API keys out of screenshots and support messages.