Skip to main content

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
Think of forms as blueprints that tell GoBlue how to process incoming data and convert it into personalized messages.

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:
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
Used for personalizing messages with {{firstName}} variables.
Used for personalizing messages with {{lastName}} variables.
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:
Hi {{firstName}}, 

Thanks for your interest in {{serviceType}}! 

I'll be in touch within 24 hours to discuss your {{projectType}} project.

Best regards,
{{agentName}}
Variable Syntax:
  • 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.
Use camelCase naming (e.g., serviceType, phoneNumber) for consistency with JSON data.

Field Naming Best Practices

  • Be Descriptive: Use companyName instead of company
  • Stay Consistent: Use the same naming convention across all forms
  • Avoid Spaces: Use firstName not first name
  • Match External Systems: Align with your CRM or form builder field names

Removing Fields

Removing a field will break any message templates that reference it. Update your templates before removing fields.

Webhook URL Structure

Each form generates a unique webhook URL:
https://api.goblue.app/v1/forms/{form-id}/webhook

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:
{
  "firstName": "John",
  "lastName": "Doe",
  "phoneNumber": "+1234567890",
  "serviceType": "Web Development",
  "companyName": "Acme Corp",
  "customField": "Any additional data"
}
The phoneNumber field is required. All other fields are optional but should match your form configuration.

Form Status Management

Capturing States

  • Form accepts webhook data
  • Messages are queued for sending
  • Appears with green “Active” badge
  • 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:
  1. Creating separate forms for different scenarios
  2. Using webhook logic to route data to appropriate forms
  3. Customizing message templates based on field values

Integration Patterns

Lead Capture Flow:
Website Form → Zapier → GoBlue Form → iMessage
CRM Integration:
CRM New Contact → Webhook → GoBlue Form → Welcome Message
Event Registration:
Eventbrite → Make.com → GoBlue Form → Confirmation Message

Troubleshooting Forms

Common Issues

Check:
  • Form capturing is enabled
  • Phone numbers are valid format
  • iOS Shortcuts are properly configured
  • Message templates don’t have syntax errors
Verify:
  • Variable names match form field names exactly
  • JSON data includes the referenced fields
  • No typos in curly brace syntax
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

Next Steps