Veridomo sends webhooks. Every CRM accepts them. No connectors. No code. Just a URL.
When you create a challenge, include a webhook URL. Veridomo POSTs the result when verification succeeds or expires. Your CRM receives a clean JSON payload. No polling. No cron jobs.
Webhook payload
Creating a challenge with a webhook
1. Go to Automations → Workflows
2. Create a new workflow, trigger: "Webhook"
3. Copy the generated webhook URL
4. Use it as webhook_url in your challenge
5. Map domain, status, verified_at to contact properties
1. Setup → Outbound Messages → New
2. Select object (e.g., Account), configure endpoint URL
3. Or use Flow Builder: new Record-Triggered Flow
4. Add an HTTP Callout action pointing to your webhook receiver
5. Parse domain into Account.Domain__c custom field
1. Admin → Extensions → Webhooks
2. Create webhook, endpoint: your receiver URL
3. Use in a Trigger: "Notify active webhook" action
4. Pass domain and status as JSON body
5. Create or update a ticket when domain is verified
1. Create a new Zap, trigger: "Webhooks by Zapier"
2. Choose "Catch Hook", copy the webhook URL
3. Use it as webhook_url in your challenge
4. Add actions: update HubSpot contact, Salesforce lead, Slack message
5. No code. Works with 5,000+ apps.
Here's what your customer sees when you whitelabel Veridomo inside your SaaS:
They enter mybrand.com in your settings page. Your backend calls POST /challenge with a webhook URL pointing to your CRM.
The challenge response includes ready-to-copy DNS records. You display them in your UI. Your customer adds the TXT record at their DNS provider.
Veridomo detects the record, POSTs to your webhook. Your CRM marks the domain as verified. Your customer's account is activated. No one wrote a script.