Workflow examples for common field service tasks | FieldCamp

Build four practical FieldCamp workflows for completed jobs, new requests, unpaid invoices, and Inbox replies using the actions available in the workflow builder.

Use these examples as starting points for workflows your team can test and adapt. Each example uses triggers and actions currently available in Settings → Workflow Automation.

Test Run performs real actions, including sending messages and changing records. Use a safe test record and test recipients before you activate a workflow. Follow the workflow building guide for the complete setup and testing process.

Send an email when a job reaches a status

Use this workflow to send a completion message, handoff note, or internal update when a job moves to a specific status.

Component	Selection
Trigger object	Job
Trigger event	Status Changed
Trigger filter	Choose the destination status, such as your completed status
Action	Send Email

Create the workflow

Open Settings → Workflow Automation, select Create New Workflow, and give the workflow a clear name such as “Email after job completion.”

Configure the trigger

Add When This Happens, choose Job, and select Status Changed. Set the To value to the status that should send the email.

Configure the email

Add Do Something, select Send Email, and choose the recipient. Write the subject and message, then insert record fields from the variable picker instead of typing variable names manually.

Test and activate

Run the workflow against a test job and confirm the recipient, content, and trigger status. Activate it only after the test result is correct.

Follow up on every new request

This workflow acknowledges a new request and creates a follow-up for the office team. Requests support communication and follow-up actions, but they do not currently offer Assign Technician or a generic Send Notification action. Review the request workflow before deciding which team process should happen next.

Component	Selection
Trigger object	Request
Trigger event	Record Created
Action 1	Send Email
Action 2	Create Follow-Up

Choose the new-request trigger

Add When This Happens, choose Request, and select Record Created.

Send the acknowledgement

Add Send Email, choose the customer recipient, and write a short acknowledgement. Use the variable picker for request and customer details.

Add the office follow-up

Add another Do Something step and select Create Follow-Up. Configure the follow-up details shown in the builder.

Test the full sequence

Use a safe test request and email address. Confirm that the email is delivered and that the follow-up appears on the correct record before activation.

Remind customers about unpaid invoices

A Recurring Schedule can query invoice records and run an action for invoices that match the configured date range and filters. This is useful for a repeatable payment-reminder process. Make sure the invoice is ready for customer delivery using the invoice creation guide.

Component	Selection
Trigger event	Recurring Schedule
Query entity	Invoice
Query filters	Select the relevant date field and set Payment Status to Unpaid
Action	Send Email

Set the recurring schedule

Add When This Happens and choose Recurring Schedule. Set the recurrence and time for your reminder run.

Target the right invoices

Choose Invoice as the query entity. Select the appropriate date field and range, then add a filter where Payment Status equals Unpaid. Add a document-status filter if your process requires one.

Write the reminder

Add Send Email, choose the customer recipient, and write the reminder. Insert invoice and customer values with the variable picker.

Verify the query before activation

Test with records that cannot contact real customers. Check that paid, partial, or out-of-range invoices do not match your filters.

Reply automatically to a new Inbox message

Inbox triggers let a workflow react to a customer message or conversation event. The Reply to conversation action sends the response on the conversation’s existing channel and keeps it in the same thread. Learn how channels and conversations work in the Inbox overview.

Component	Selection
Trigger event	Inbox — Customer message received
Optional step	Delay
Action	Reply to conversation

Use a name that explains both the trigger and outcome.
Limit each workflow to one clear business outcome.
Confirm every recipient, status, filter, and delay with a test record.
Review the execution result after activation and correct failed steps promptly.
Disable workflows that no longer match your operating process.

Workflow Automation overview