Send participant data to a webhook

Prepare a public receiving endpoint

Open Integrations → Webhook and enter Webhook URL. Use an HTTPS endpoint controlled by your organization. Revup rejects private or reserved network destinations. The connector exposes a URL; it does not provide custom authentication headers or a signing-secret setting. Do not assume the request carries a Revup signature.

Choose data and understand delivery

Review the field mapping before enabling delivery. The connector sends JSON using POST, with account, promotion, participant, primary-field, system-field, and selected custom-field information. Normal participant delivery uses the event type entrant.processed; a completed payment can produce the separate entrant.payment_paid event.

Core/system mappings are fixed where shown; custom fields use their configured keys. Avoid sending personal data or participant login links your receiving workflow does not need. A participant login link can grant access to that participant's session and should be treated as confidential.

Your receiver should accept the expected JSON, respond promptly with a successful status, and tolerate repeated deliveries without repeating a business action. Keep processing bounded and monitor failures. Because this connector has no configurable request signature, do not make a sensitive decision based solely on an unauthenticated payload.

Test the full path

Submit a staging participant, inspect the received fields, and confirm the delivery status in Revup. Test a payment event separately if applicable. After correcting a failed destination or mapping, retry an eligible failed delivery from the participant detail.

The Send Webhook step in Flows is a different feature with its own event timing and POST/PUT choice.