Best Practices

Recommended setup

Use an Administrator Application Password

Create a dedicated Application Password under an Administrator account so Coupler.io can access all post statuses, private pages, and user data. A lower-privilege account will silently exclude content you might expect to see.

Join Posts with Categories and Users

Posts alone only give you category and author IDs. Add Categories, Tags, and Users as additional sources in your data flow and use the Join transformation to get human-readable names alongside your post data.

Use Append mode for comment tracking

If you're monitoring comments over time, set your data flow to Append mode so new comments accumulate in your destination rather than replacing the previous snapshot.

Data refresh and scheduling

Match refresh frequency to publish cadence

If your site publishes a few posts per week, a daily refresh is more than enough. High-volume news sites may benefit from hourly refreshes for the Posts entity.

Use date filters for large comment volumes

For sites with thousands of comments, set a start date on the Comments entity to limit how far back Coupler.io looks. This keeps refresh times short and your destination focused on recent engagement.

Performance optimization

Split entities across separate data flows

If you need Posts for one team and Media for another, create separate data flows rather than combining everything. This makes troubleshooting easier and keeps each destination clean.

Send content to AI for analysis

Export your Posts entity to ChatGPT, Claude, or Gemini to automate SEO audits, generate meta descriptions, or classify posts by topic — without touching your live WordPress site.

Common pitfalls

If your site uses Cloudflare, its bot protection can block Coupler.io from reaching the WordPress REST API. You'll get a "non-JSON response" error. Check your Cloudflare firewall rules and add an exception for the /wp-json/ path before spending time debugging elsewhere.

Do

• Use an Application Password, not your WordPress login password

• Verify your site URL is publicly accessible before connecting

• Join Posts + Users + Categories for complete reporting datasets

• Test with a manual run before scheduling

Don't

• Use a Subscriber or Contributor account for the API connection — you'll miss private content

• Rely on the start date filter for Posts — it only works for Pages, Comments, Media, and Editor blocks

• Store sensitive site credentials in shared spreadsheets alongside your exported data