How to Connect FieldPulse

By connecting FieldPulse to LaunchSMS, you can create FieldPulse customers and jobs from LaunchSMS forms and send FieldPulse job updates back into LaunchSMS for automations and content workflows.

How to enable this feature?

Log into the LaunchSMS admin dashboard and go to Integrations and select FieldPulse.

On the FieldPulse integration page, enter your Company API Key and save the integration.

You can also set these optional defaults while connecting:

• Default Job Type
• Default Job Status
• Billing Code
• Include referral / UTM details in job notes

When you save, LaunchSMS will test the API key. If the key is valid, the integration will show as connected and LaunchSMS will generate your unique webhook URL.

Add the FieldPulse webhook

Once the integration is saved, copy the Webhook URL shown on the FieldPulse integration page in LaunchSMS.

Add that webhook URL inside FieldPulse so job status updates can be sent back into LaunchSMS.

LaunchSMS stores recent webhook activity so you can confirm that events are being received.

What LaunchSMS sends to FieldPulse

When a LaunchSMS form is configured to send submissions to FieldPulse, LaunchSMS can create a customer and job using the mapped form fields.

Common mappings include:

• Customer first name
• Customer last name
• Email
• Phone
• Street address
• City
• State
• ZIP code
• Job type
• Preferred booking date
• Preferred booking window

If a form does not provide a mapped job type or status, LaunchSMS can fall back to the defaults saved in the FieldPulse integration settings.

Form Builder setup

Open your LaunchSMS form in Form Builder and enable Send Submissions to FieldPulse.

Map the required customer fields and the job fields you want to pass into FieldPulse.

At minimum, you should map:

• Customer first name
• Customer last name
• Customer phone
• Street
• City
• State
• ZIP code

If you want cleaner booking data, also map:

• Customer email
• Job type
• Booking date
• Booking time or preferred window

How it works

After the integration is connected:

1. A customer submits a LaunchSMS form.
2. LaunchSMS creates the customer and job in FieldPulse.
3. FieldPulse sends job status webhooks back to LaunchSMS using your webhook URL.
4. LaunchSMS can use those events for automations, job follow-up, and Local Content Engine workflows when enabled.

Troubleshooting

If FieldPulse is not connecting or syncing correctly, check the following:

• The FieldPulse API key is valid
• The integration page shows Connected
• The webhook URL from LaunchSMS was added in FieldPulse
• Your form has Send Submissions to FieldPulse enabled
• Required customer and address fields are mapped in Form Builder
• Default Job Type, Status, and Billing Code are set correctly if your form is not mapping them directly

Related guides

• FieldPulse Integration – User Guide
• How to Setup Local Content Engine with FieldPulse