Integrations
Google Search Console, webhooks, and CMS integrations
Wyrote integrates with external services to enhance your content workflow. Connect Google Search Console for search analytics, set up webhooks for automated publishing, and explore CMS integrations.
Accessing Integrations
- Click Settings in the sidebar navigation.
- Select the Integrations tab.
Google Search Console
Connect your Google Search Console account to track how your content performs in Google search results.
Connecting GSC
- Click Connect Google Search Console.
- A popup window opens for Google OAuth authorization.
- Sign in to your Google account and grant Wyrote read-only access to Search Console data.
- After authorization, a list of your GSC properties appears.
- Select the property URL that matches your domain.
- Click Connect.
Once connected:
- A green checkmark confirms the connection
- The connected property URL is displayed
- The Search Performance tab becomes available in Analytics
Disconnecting GSC
- Click the Disconnect button next to the connected property.
- Confirm the disconnection.
This removes the GSC connection but does not revoke Google permissions. To fully revoke, visit your Google account security settings.
Note: Wyrote only requests read-only access. It cannot modify any data in your Search Console.
Webhooks
Set up webhooks to receive automated notifications when content is ready or published. This enables integration with any CMS, automation platform, or custom system.
Setting Up a Webhook
- Navigate to the Webhook sub-tab in Integrations.
- Enter your Webhook URL — the endpoint that will receive POST requests.
- Optionally enter a Webhook Secret — used to verify the authenticity of incoming requests.
- Click Save.
How Webhooks Work
When an article's status changes to ready or published, Wyrote sends a POST request to your webhook URL containing:
- Article title and content (HTML and markdown)
- Meta description and slug
- Featured image URL
- Primary and secondary keywords
- Structured data (JSON-LD)
- Full article metadata
Webhook Security
If you set a webhook secret:
- Each request includes a signature header
- Verify the signature on your server to confirm the request came from Wyrote
- This prevents unauthorized parties from sending fake webhook payloads
Common Webhook Integrations
Use webhooks with automation platforms to push content to your CMS:
- Zapier — Create a Zap that triggers on webhook receipt and publishes to your CMS
- Make (Integromat) — Build a scenario that processes webhook data and pushes to WordPress, Webflow, etc.
- Custom scripts — Build your own handler to receive and process content
WordPress
Wyrote has a native WordPress integration via the Wyrote Publisher plugin. Articles are automatically sent to your WordPress site when they reach ready or published status.
Setup Guide
- Download and install the Wyrote Publisher plugin on your WordPress site.
- In your WordPress admin, go to Settings > Wyrote Publisher.
- Copy the Webhook Endpoint URL shown in the plugin settings (it looks like
https://yourblog.com/wp-json/wyrote/v1/publish). - In Wyrote, go to Settings > Integrations > WordPress tab.
- Paste the endpoint URL into the Webhook Endpoint URL field.
- Click Generate to create a webhook secret, then copy it and paste it into the plugin settings on WordPress.
- Click Save Changes in Wyrote.
- Click Test Connection to verify everything works.
WordPress vs. Custom Webhook
You can use either WordPress or a custom webhook, but not both at the same time:
- Switching to WordPress replaces any existing webhook configuration
- Switching to a custom webhook replaces the WordPress connection
- A warning message is shown when switching between the two
Webhook Secret
The webhook secret ensures only Wyrote can send content to your WordPress site:
- Click Generate to create a secure secret
- Use the eye icon to show/hide the secret
- Use the copy icon to copy it to your clipboard
- Paste the same secret in both Wyrote and the WordPress plugin settings
Test Connection
After saving your settings, click Test Connection to verify the integration:
- A green message confirms a successful connection
- A red message indicates an error — check that the URL and secret match on both sides
Recent Deliveries
The Recent Deliveries section shows a log of all webhook requests sent to your WordPress site:
| Column | Description |
|---|---|
| Status icon | Green checkmark (success) or red X (failure) |
| Event | Test or Publish |
| Article | The article title that was sent |
| HTTP Status | Response code (200 = success, 4xx/5xx = error) |
| Duration | How long the request took (in milliseconds) |
| Time | When the delivery was sent |
Hover over the HTTP status badge to see the full response body — useful for debugging failed deliveries.
Click Refresh to reload the delivery log.
Troubleshooting
| Problem | Solution |
|---|---|
| Test connection fails | Verify the endpoint URL matches exactly what the WordPress plugin shows |
| 401 / 403 errors | Check that the webhook secret matches on both sides |
| 404 errors | Make sure the Wyrote Publisher plugin is activated on WordPress |
| Timeout errors | Check your WordPress server's firewall and PHP timeout settings |
Other CMS Integrations
Additional CMS integrations are planned:
| CMS | Status |
|---|---|
| Framer | Coming Soon |
| Wix | Coming Soon |
| Webflow | Coming Soon |
| Ghost | Coming Soon |
| Shopify | Coming Soon |
In the meantime, use Webhooks + Zapier/Make to automate content publishing to any CMS not listed above.
Integration with Automations
Webhooks work hand-in-hand with Automation modes:
- Manual mode — Webhooks fire when you manually publish
- Scheduled mode — Webhooks fire when auto-approved content is ready
- Auto mode — Webhooks fire automatically for both ready and published events, enabling fully hands-off content publishing
Next Steps
- Automations — Configure automatic content approval and publishing
- Search Performance — View GSC data after connecting
- Content View — Understand content publishing