This guide explains how to connect FieldPulse to Local Content Engine.
What FieldPulse Can Drive
When FieldPulse is connected, Local Content Engine can use qualifying job activity to:
- Create mini jobs
- Generate AI summaries and titles
- Feed content into service-area and service pages
- Generate AI images if enabled
- Generate AI recap videos if enabled
- Trigger downstream automations
Prerequisites
Before setup, make sure you have:
- A FieldPulse account
- Your company FieldPulse API key
- Access to configure webhooks in FieldPulse
- Local Content Engine enabled in LaunchSMS
Step 1: Connect FieldPulse in LaunchSMS
- Go to Settings > Integrations
- Open FieldPulse
- Enter your Company API Key
- Review or set optional defaults:
- Default Job Type
- Default Job Status
- Billing Code
- Include referral / UTM details in job notes
- Save the integration
LaunchSMS will test the connection when the key is saved.
Step 2: Add the Webhook URL in FieldPulse
After the integration is saved, copy the webhook URL shown on the FieldPulse integration screen.
Add that URL in FieldPulse so status updates are sent back into LaunchSMS.
Step 3: Enable FieldPulse in Local Content Engine
- Open Local Content Engine
- Turn on Enable Local Content Engine
- Turn on Use Queue Processing
- Turn on the FieldPulse provider toggle
Optional:
- Enable AI image creation
- Enable AI video creation
- Enable automation trigger for GBP syndication
- Add a WordPress sync webhook URL
Step 4: Configure Brand Assets
If you want branded media generation, configure:
- Primary Logo Attachment
- Secondary Reference Attachment
- Aspect ratio
- Duration
- Resolution
Step 5: Run a Test Job
Run a test workflow that produces usable completed-job content and verify that FieldPulse activity is reaching LaunchSMS.
Then confirm:
- A mini job is created
- The service type is correct
- The city and state are correct
- Images and/or videos generate if enabled
- Automations fire if configured
Best Practices
To improve content quality from FieldPulse:
- Use consistent job type naming
- Keep addresses complete and normalized
- Add meaningful field notes or job notes
- Use media when available
- Leave queue processing enabled in production
Troubleshooting
If FieldPulse is not creating Local Content Engine content, check:
- The API key is valid
- The integration shows connected
- The webhook URL is installed in FieldPulse
- Local Content Engine is enabled
- The FieldPulse provider toggle is on
- Queue workers are running if queue mode is enabled