Before you create a Trigger button custom field or configure an automation rule under Triggers and actions that posts to a webhook, you must first complete the webhook URL domain verification process. Scoro validates the target webhook URL at the exact moment you save your setup, so verification must be completed in advance to prevent validation errors.
Jump to...
1. Why is webhook URL verification required?
Webhook URL verification ensures that your automated workflow data will be sent securely and accurately. Scoro performs two checks to protect your data and confirm authorization:
URL status check: Verifies that the endpoint is an active, working URL by confirming it returns a successful status code (200).
Domain ownership check: Verifies that your team has authorized access to add data to the destination URL, preventing data from being sent to unauthorized endpoints.
Note! You must complete the domain verification steps before saving your custom field or an automation rule via Triggers and actions. Scoro runs this validation check at the exact moment you click Save. If the domain ownership cannot be verified at that moment, saving will fail with a validation error.
2. Methods for verifying domain ownership
You can verify your domain authorization using one of the following two options, and this must be completed on the domain where the webhook URL is hosted:
Unsure how to proceed with either of these options? If you are unfamiliar with modifying server files or DNS records, you can:
Forward these instructions to your company’s web developer, site administrator, internal IT support, or domain administrator
Consult the help center for your specific domain registrar or hosting provider (such as GoDaddy, Cloudflare, or Namecheap) for step-by-step instructions on uploading a file to the root directory or adding a TXT record.
Method 1: Add a verification file to the root folder
To verify a webhook URL by adding a TXT file to the root folder:
- Create a plain text file named scoro.txt.
- Upload this file directly to the ROOT folder of your site or application directory.
- Ensure the file is publicly reachable at its root file path (e.g., https://yourdomain.com/scoro.txt).
Method 2: Add a DNS record
To verify a webhook URL by adding a DNS record:
- Access your domain's DNS management platform.
- Create a new TXT record within your domain's DNS settings. The TXT record must be added to the exact address (host/subdomain) used in the webhook URL, not necessarily the main root domain. For example, if your webhook URL is https://hooks.mycompany.com/..., the TXT record needs to be added specifically under hooks.mycompany.com. Adding it only under mycompany.com will not work.
- Input scoro.txt as a line within the record value.
3. Verification exceptions
Scoro skips the webhook URL status and domain ownership checks for certain whitelisted domains. These are typically well-known automation/integration platforms or developer tools – such as Zapier, n8n, Airtable, Make, etc. – that Scoro has pre-approved, allowing you to connect to those URLs directly and bypass those checks.