Zapier, Make & n8n Integration

Webhook Integration empowers you to bridge your ChromePilot browser assistant directly with the world's most powerful automation platforms—Zapier, Make, and n8n. By configuring a custom webhook URL and providing a clear Description, you can transform conversational requests in your sidebar into fully automated actions that trigger across thousands of third-party applications.

The Description field is highly important. ChromePilot uses this description to dynamically teach its AI when to use your webhook. For example, if you set the description to "Creates a new Jira ticket and sends a Slack message", the AI will automatically route relevant user requests to your webhook endpoint—securely packaging the necessary details into a standard JSON payload.

Understanding the Webhook Payload Structure

To successfully integrate ChromePilot with your automation platform, your endpoint must be configured to accept a POST request with a JSON body. The data structure sent by ChromePilot includes a single "query" field (a smart string generated by the AI containing all parsed instructions and details), a "timestamp" (ISO format), a "source" identifier (always "chromepilot"), and a "metadata" object. During manual connection tests, `metadata.test` will be set to `true` so your automation can distinguish test pings from real AI commands.

Troubleshooting Webhook Connection Issues

If your automation fails to trigger, the most common issue is improper data mapping on the receiving end. Double-check within your platform—such as the "Catch Hook" trigger in Zapier, the "Custom Webhook" module in Make, or the "Webhook" node in n8n—that it correctly parses the incoming JSON request and properly maps the "query" field to the subsequent steps in your automation flow.

Always utilize ChromePilot's built-in "Test Connection" button before relying on the AI. If the test fails, double-check your target URL for typos and confirm that your platform's webhook endpoint is actively listening. If the test succeeds but the AI workflows don't trigger, ensure your webhook Description is detailed enough for the AI to understand its purpose, and verify that your automation platform is returning a valid HTTP response (like a 200 OK).