for custom-stack developer
verify HMAC-signed article payloads, queue drafts for human approval, and write approved posts into your site data store using the live AutoSEO article, approval, cadence, and connector corpus.
overview
A webhook blog publisher receives signed article payloads from external systems, verifies the HMAC signature, and stores the content as a draft in your site data store. It hands each draft to the AutoSEO article and approval pipeline so humans review content before publication.
The workflow preserves cadence and connector metadata from the connector corpus, and it prevents unattended publishing. Use it to move content from content sources into your editorial queue, not to bypass manual review.
security first
Validate the HMAC signature on the raw request body using a shared secret and a constant-time comparison. Reject requests that fail signature, timestamp, or replay checks to keep unverified content out of your draft store.
Complement signature checks with sender allowlists, TLS client validation where available, and payload size limits. Log validation outcomes for audit and set up a retry policy for transient errors at the sender side.
implementation guide
Parse the signed article payload into your content schema, sanitize fields that accept HTML, and extract SEO metadata. Store the content as a draft record that includes source, raw payload, validation status, and suggested cadence.
Attach connector corpus hints so the AutoSEO engine knows recommended cadence and publishing connectors. Do not publish drafts directly. Instead, add them to the single approval queue for human review and scheduling.
ops and reliability
Make webhook handling idempotent by using a unique payload id or external reference. A repeated delivery should update or noop, not create duplicate drafts. Record processing state so retries do not alter approvals unintentionally.
Monitor endpoint health, signature failures, and queue growth. Surface processing errors to the editorial team and ensure the AutoSEO approval queue remains the single source of truth for drafts pending publish.
integration
The webhook blog publisher hands drafts into the live AutoSEO article and approval workflow. Include connector hints in the payload so the platform can suggest cadence, target connectors, and approval routing without publishing automatically.
AutoSEO prepares article drafts and uses the connector corpus to suggest where and when posts should publish. Final publication requires human approval. The publisher is for arriving content, not for unattended publishing guarantees.
Questions for this workflow
Include the signature header with the HMAC-SHA256 hex or base64 of the raw request body, a timestamp header to limit replay, and a unique payload id. Your receiver should compute the HMAC using the shared secret and compare in constant time.
No. The webhook blog publisher writes drafts and enqueues them for the AutoSEO approval workflow. Human approval is required before articles are published. This prevents unattended publishing and preserves editorial control.
Use a unique external id in the payload to detect duplicates. On first processing, create the draft and store the external id. On subsequent deliveries, look up the id and update the existing draft or return a no-op response. Log decisions so retries are traceable.
Include cadence and connector hints in the payload so AutoSEO can suggest posting frequency and targets from the connector corpus. The webhook publisher preserves those hints when saving drafts, and the AutoSEO approval flow uses them to recommend scheduling after human approval.
Start with the workflow above, keep the human review gate, and adapt the cadence to the accounts you actually operate.
Start a review-first workflow