What are Forms?
Forms in GoBlue are the foundation of your message automation system. They define:- Data Structure: What information you collect from leads or contacts
- Message Templates: How your automated messages are personalized
- Automation Rules: When and how messages are sent
- Webhook Endpoints: Where external data enters your system
Form Components
Basic Information
Every form includes:Form Name
A descriptive identifier to help you organize multiple forms
Webhook URL
A unique endpoint where external services send data
Data Fields
Forms collect specific pieces of information:Phone Number (Required)
Phone Number (Required)
The recipient’s phone number in any standard format. GoBlue automatically normalizes phone numbers for iMessage delivery.Accepted Formats:
- +1234567890
- (123) 456-7890
- 123-456-7890
- 123.456.7890
First Name (Optional)
First Name (Optional)
Used for personalizing messages with
{{firstName}} variables.Last Name (Optional)
Last Name (Optional)
Used for personalizing messages with
{{lastName}} variables.Custom Fields
Custom Fields
Add any additional data fields you need for your workflow:
- Email addresses
- Company names
- Service types
- Custom notes
- Dates and times
Form Configuration
Message Templates
Create dynamic message templates using variable substitution:- Use double curly braces:
{{variableName}} - Variable names must match your form field names exactly
- Variables are case-sensitive
- Undefined variables are left blank in the final message
Automation Settings
Enable Capturing
Turn on/off data collection for this form
Auto Follow-up
Automatically send messages when data is received
Send Later
Delay message delivery by minutes, hours, days, or weeks
Include Attachment
Add GIFs or other media to your messages
Form Field Management
Adding Fields
1
Open Form Editor
Navigate to your form and tap “Edit” or the pencil icon.
2
Add Field
Tap “Add Field” in the Form Fields section.
3
Name Your Field
Choose a descriptive name that’s easy to remember for message templates.
Field Naming Best Practices
- Be Descriptive: Use
companyNameinstead ofcompany - Stay Consistent: Use the same naming convention across all forms
- Avoid Spaces: Use
firstNamenotfirst name - Match External Systems: Align with your CRM or form builder field names
Removing Fields
Webhook URL Structure
Each form generates a unique webhook URL:URL Components
- Base URL:
https://api.goblue.app/v1/forms/ - Form ID: Unique UUID identifier for your form
- Endpoint:
/webhook- the data submission endpoint
Expected JSON Format
Send data to your webhook URL as JSON:The
phoneNumber field is required. All other fields are optional but should match your form configuration.Form Status Management
Capturing States
Active (Capturing Enabled)
Active (Capturing Enabled)
- Form accepts webhook data
- Messages are queued for sending
- Appears with green “Active” badge
Inactive (Capturing Disabled)
Inactive (Capturing Disabled)
- Webhook requests are ignored
- No messages are generated
- Useful for testing or maintenance
Advanced Form Features
Conditional Logic
While not directly configurable in the UI, you can implement conditional message sending by:- Creating separate forms for different scenarios
- Using webhook logic to route data to appropriate forms
- Customizing message templates based on field values
Integration Patterns
Lead Capture Flow:Troubleshooting Forms
Common Issues
Messages Not Sending
Messages Not Sending
Check:
- Form capturing is enabled
- Phone numbers are valid format
- iOS Shortcuts are properly configured
- Message templates don’t have syntax errors
Variables Not Replacing
Variables Not Replacing
Verify:
- Variable names match form field names exactly
- JSON data includes the referenced fields
- No typos in curly brace syntax
Webhook Not Receiving Data
Webhook Not Receiving Data
Confirm:
- Correct webhook URL is being used
- JSON payload is valid
- Content-Type header is set to application/json
Best Practices
Naming Convention
Use consistent, descriptive names for forms and fields
Template Testing
Test message templates with sample data before going live
Field Validation
Validate required fields in your external systems
Documentation
Document your form configurations for team members