Ensuring a Seamless WordPress Connection with OttoKit

OttoKit thrives on communication, not just with users, but with the tools and platforms you already use. When integrating with WordPress, OttoKit taps into your site’s REST API to establish a smooth and secure connection. But what happens when something blocks that connection? Let’s walk through how to identify and resolve issues that might be standing in your agent’s way.

Understanding the WordPress Connection Requirement
OttoKit uses the WordPress REST API to connect with your site and interact with installed plugins. If that API is restricted — whether by a plugin, server firewall, or misconfiguration — your OttoKit workflows may hit a roadblock.

You might even see a confusing message like this one below, despite having the plugin installed and active:
 

But not every OttoKit integration relies on this connection. SaaS-based platforms often use an API key or OAuth authentication. These cloud-native methods don’t require REST API access and typically work without issue.

Troubleshooting the Blocked Connection
Here’s how to get your WordPress connection back on track:

1. Check for Security or Performance Plugins
Powerful plugins like Perfmatters, WordFence, or Cloudflare can sometimes do too good a job. While they’re excellent for protection and optimization, they can also disable REST API routes or block traffic from unfamiliar IP addresses, including OttoKit’s.

2. Review Their Settings or Traffic Logs
If one of these plugins is active, inspect its settings for REST API restrictions or view the live traffic logs. Look for blocked requests or suspicious IP bans related to OttoKit.

3. Whitelist the OttoKit IP Address
If your plugin firewall is the culprit, adding OttoKit’s IP address to the allowlist usually resolves the issue. This tells your security plugin: “Hey, this one’s friendly.”

4. Talk to Your Hosting Provider
If no plugin seems responsible, your host may run a server-level firewall. Ask them to check server logs and confirm if OttoKit’s IP is being blocked. If so, they can easily whitelist it to restore communication.

Pro Tip: If you’re unsure which IP address OttoKit is using or what needs to be whitelisted, contact our support team, and we’ll guide you through it.

Not All Connections Are Affected
Remember, this issue only affects WordPress REST API-based connections. Integrations that rely on API keys or OAuth (like Slack, WhatsApp, or Salesforce) are not impacted and will continue working without interruption.

Test Before You Stress
Once you’ve made the necessary adjustments, run a test connection inside OttoKit. You should now be able to progress to the configuration tab for that trigger or action in your workflow.