How to Use the Inbound Webhook Automation Trigger

Inbound Webhooks let you automatically send data from external systems directly into Enrollio. When something happens in another platform—like a form submission, payment confirmation, or event registration—that system can instantly notify Enrollio and trigger an automation.

This real-time data transfer keeps your parent records up-to-date, reduces manual data entry, and helps your team respond faster to new inquiries and enrollments.

What is an Inbound Webhook?

An Inbound Webhook is a unique URL that receives data from external systems. When an event occurs in another platform, it sends an HTTP request (POST, GET, or PUT) to your webhook URL, instantly triggering an automation in Enrollio.

Think of it as a mailbox where other systems can drop off information. Once Enrollio receives that data, you can use it to update parent records, send notifications, log activities, or trigger follow-up actions.

Practical Uses for Childcare Centers

Here are some real-world scenarios where Inbound Webhooks can streamline your operations:

Online Tour Registration

When a parent registers for a tour through an external event platform, the webhook can automatically create their record in Enrollio and send a confirmation text message.

Example: Your event platform sends tour registration details (parent name, email, phone, tour date) to Enrollio. The automation creates or updates their parent record and adds the tour to your calendar.

Payment Processing Integration

Connect your payment processor to Enrollio so that when a parent pays a registration fee, their enrollment status updates automatically.

Example: Your payment system sends transaction details to Enrollio. The automation updates the parent's record with payment information and moves them to the next stage in your enrollment pipeline.

Waitlist Form Submissions

Capture waitlist requests from forms on your website or social media and automatically add them to Enrollio.

Example: A parent submits a waitlist form. Your form platform sends their information to Enrollio, which creates their record, adds them to the appropriate waitlist, and triggers a welcome email.

Support Ticket Integration

If you use a separate customer support system, webhook data can link support tickets to parent records in Enrollio.

Example: A parent creates a support ticket. Your ticketing system sends the details to Enrollio, which associates the ticket with their record so your team has complete context.

How to Set Up an Inbound Webhook Trigger

Setting up your webhook takes three simple steps:

Step 1: Get Your Webhook URL

1. Create a new automation in Enrollio
2. Select "Inbound Webhook" as your trigger
3. Copy the webhook URL that appears
4. Paste this URL into your external system or application
5. Click "Test Trigger" to verify the connection

[SCREENSHOT: Automation builder showing Inbound Webhook trigger selection with webhook URL visible and Test Trigger button highlighted]

Your external system will use this URL to send data to Enrollio using POST, GET, or PUT requests.

Step 2: Capture Sample Data

Now you'll test the webhook and save a sample of the data format:

1. Send a test request from your external system to the webhook URL
2. In Enrollio, you'll see the incoming data appear
3. Review the data fields to make sure everything looks correct
4. Click "Load More" if you need to see additional recent requests
5. Select the sample data you want to use as your reference
6. Save the trigger

[SCREENSHOT: Webhook trigger interface showing received sample data with fields like name, email, phone visible, and Load More and Save buttons]

When you save this sample data, Enrollio creates custom value references. You can use these references throughout your automation just like any other custom field.

Step 2.1: Send Your Test Request

From your external system, send a POST, GET, or PUT request to the webhook URL you copied. The response will include a unique ID—save this for the next step.

Step 2.2: Find Your Request

Copy the unique ID from your test request and use it to search for the correct data mapping in your webhook trigger. This ensures you're referencing the right sample.

Step 2.3: Verify the Data

Select your request and review the body to confirm all the data fields are correct before proceeding.

Step 3: Map Data to Parent Records

After saving your trigger, Enrollio will prompt you to add a "Create/Update Parent" action:

1. Select which fields from the webhook data should map to parent record fields
2. For example, map "first_name" from the webhook to "First Name" in Enrollio
3. To create or update a parent record, you must include either email or phone

[SCREENSHOT: Create/Update Parent action showing field mapping interface with webhook custom values being mapped to parent fields like Email, Phone, First Name]

Using Webhook Data in Your Automations

Once you've captured webhook data, you can use it throughout your automation in any action.

In Text Messages and Emails

Insert webhook custom values into your messages just like any other field:

Example: "Hi {{webhook.first_name}}, thank you for registering for a tour on {{webhook.tour_date}}. We'll see you soon!"

[SCREENSHOT: SMS action with custom value dropdown showing webhook fields like webhook.first_name, webhook.tour_date being inserted into message text]

In Conditional Logic (If/Else)

Create conditions based on webhook data to route your automation differently:

Example: If {{webhook.program_type}} equals "Infant Care", send information about your infant program. Otherwise, send general enrollment information.

[SCREENSHOT: If/Else action showing condition builder with webhook.program_type being compared to "Infant Care"]

Running Automations Without Parent Records

Your automations can run even if the webhook data doesn't create or update a parent record. This is useful when you just need to log information or notify your team.

Actions that work without parent data include:

• Custom Webhook (send data to another system)
• Google Sheets (log data to a spreadsheet)
• Slack notifications
• ChatGPT actions
• Internal notifications

Example: Receive enrollment data via webhook, add the information to a Google Sheet for tracking, categorize based on program type using If/Else, and send a Slack notification to the appropriate staff member—all without creating a parent record.

Important Considerations

• Test thoroughly: Always send test requests before going live to ensure data maps correctly
• Secure your webhook URL: Treat it like a password—only share it with trusted systems
• Monitor executions: Keep track of how many webhook executions you're using each month
• Use unique identifiers: Include IDs in your webhook data to avoid duplicate records
• Check data formats: Ensure dates, phone numbers, and other fields match Enrollio's expected formats