Docs

User Guide

User Guide / Agent Workflows

Using webhooks

Sometimes the moment that should trigger an agent does not begin in Rox.

It begins in a form submission. A signup event. An internal tool. A system somewhere else in your stack.

That is where webhooks come in.

Webhook-triggered agents let an external system start an agent in Rox. Once the webhook arrives, Rox reads the payload, understands the event, and takes the right next step.

That might mean:

  • routing a signup

  • sending an alert

  • generating a summary

  • updating a record

  • launching an internal process

  • triggering downstream work from another system

How to use a webhook trigger

Step 1

Choose On Webhook Call as the trigger when building the agent.

Step 2

Copy the webhook URL or slug from the agent UI.

Webhook URLs are generated in the UI now, so most users do not need to hand-assemble the endpoint.

If you need to support authentication, check the Use auth option and a signing key will one-time appear to set in the header.

Step 3

Send a POST request with JSON data to the webhook endpoint.

For new custom agents, use the URL generated in the UI. It follows the shared webhook pattern:

curl -X POST https://.../webhooks/w/{webhook_slug} \
  -H "Content-Type: application/json" \
  -d '{"feedback":"here's some feedback"}'
curl -X POST https://.../webhooks/w/{webhook_slug} \
  -H "Content-Type: application/json" \
  -d '{"feedback":"here's some feedback"}'
curl -X POST https://.../webhooks/w/{webhook_slug} \
  -H "Content-Type: application/json" \
  -d '{"feedback":"here's some feedback"}'

Step 4

Use the payload inside the agent.

The payload can be any JSON object. That data can then be read and used in later steps.

When to use webhooks

Use a webhook-triggered agent when Rox should respond to an external event.

Examples:

  • Google Form submission

  • marketing signup

  • internal tool event

  • external system update

  • custom automation from another platform

A webhook is the outside world tapping Rox on the shoulder and saying:

This happened. Take it from here.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.