Skip to main content

ContentPen Integration

Tier: Extended — Has its own settings area, stored credentials, webhook endpoint, and light AI configuration for content formatting.

SyteOps integrates with ContentPen to build self-routing content pipelines. ContentPen generates content and sends it as a webhook. SyteOps verifies the payload, relays it to FlowMattic, and your SyteOps user and role data tells the workflow exactly what to do with it — including who it belongs to.

The result: content arrives in WordPress assigned to the right author, with fields populated and SEO metadata ready. No manual assignment. No workflow editing when authors change.

For the complete pipeline story, see Content Pipelines.

What It Does​

When ContentPen generates or processes content, it sends a webhook to your SyteOps installation. SyteOps:

  1. Verifies the webhook signature (HMAC-SHA256)
  2. Processes and normalizes the payload
  3. Relays it to the FlowMattic webhook URL you configure in the System/API tab

From there, FlowMattic handles the rest — using SyteOps variables (user data, role assignments, variable sets) to route and process the content.

Requirements​

  • SyteOps installed and activated
  • FlowMattic installed and activated
  • ContentPen integration enabled in SyteOps

Setup​

1. Enable the Integration​

  1. Navigate to the Integrations tab in SyteOps
  2. Toggle ContentPen ON
  3. Save

2. Configure API Settings​

  1. Go to the System/API tab
  2. Find the ContentPen section
  3. Enter your ContentPen webhook secret and FlowMattic relay URL
  4. Save

3. Configure Webhook URL​

In your ContentPen account, set the webhook URL to:

https://yoursite.com/wp-json/syteops-int-cp/v1/webhook

Replace yoursite.com with your actual domain.

Webhook Security​

SyteOps verifies every incoming ContentPen webhook using HMAC-SHA256 signature verification. Each webhook includes:

  • X-Contentpen-Signature — HMAC signature for payload verification
  • X-Contentpen-Event — The event type
  • X-Contentpen-Delivery-Id — Unique delivery identifier

Invalid signatures are rejected before any processing occurs.

Role-Aware Author Assignment​

The power of the ContentPen integration comes from combining it with SyteOps role data:

  • Your FlowMattic workflow references syteops_user_NNN_is_{role} variables to identify the current holder of a content role
  • ContentPen sends one webhook to one FlowMattic workflow
  • The workflow reads SyteOps role variables to determine which WordPress author to assign
  • The article lands assigned correctly — every time

When the author changes, update their role assignment in SyteOps. The next ContentPen article routes to them automatically. No workflow edits needed.

Cloudflare Configuration​

If your site uses Cloudflare, server-to-server webhook requests may be blocked by Bot Fight Mode or other security features. See the Cloudflare Setup Guide for the specific firewall rule to add.

Troubleshooting​

Webhooks Not Being Received​

  1. Check the webhook URL — Ensure it's exactly /wp-json/syteops-int-cp/v1/webhook with the correct domain
  2. Check Cloudflare — If using Cloudflare, verify the Allow rule is in place (see Cloudflare Setup Guide)
  3. Check REST API restriction — SyteOps endpoints (/wp-json/syteops-int-cp/*) should be automatically allowed, but verify in your REST API settings
  4. Check FlowMattic — Ensure FlowMattic is active and licensed, as the webhook relay depends on it

Getting 403 Errors​

This usually means Cloudflare or another security layer is blocking the request before it reaches WordPress. See the Cloudflare troubleshooting section for diagnosis steps.

Webhook Received but Not Processed​

  1. Verify the ContentPen integration is toggled ON in the Integrations tab
  2. Check that FlowMattic is active — the relay depends on FlowMattic being available
  3. Enable Debug Mode in SyteOps for detailed logging