Build and Test Workflows | FieldCamp

Create a FieldCamp workflow with record, schedule, or Inbox triggers; add object-specific actions and AI steps; then validate and run a safe test.

The FieldCamp workflow builder connects a trigger to conditions, delays, actions, and optional AI Agent steps. This guide explains the current trigger and action model and how to test a workflow before activation.

Before you build

Administrators can create and edit workflows. Custom roles need the workflow builder create or edit permission under system settings; see roles and permissions.
Connect any mailbox, phone number, WhatsApp account, or accounting service required by your actions. Use Apps & Integrations to review available connections.
Prepare a safe test record and test recipients. A workflow Test Run performs real actions.

Workflow Automation is a core feature. You do not need to enable an add-on before opening the builder.

Create a workflow

Open Settings → Workflow Automation.
Select My Workflows.
Select Create New Workflow.
Enter a clear workflow name.

The palette contains:

When This Happens under Triggers
Check If and Delay under Logic
Do Something under Actions
AI Agent under AI

Start with one When This Happens node, then connect the remaining steps in the order they should run.

Configure the trigger

Select When This Happens, then choose an event type.

Trigger	Configuration
Record Created	Choose the object whose new record should start the workflow.
Record Updated	Choose the object. Use conditions when only particular updates should continue.
Record Deleted	Choose the object whose deletion should start the workflow.
Status Changed	Choose the object and, where available, optional From stage and To stage values.
Field Changed	Choose the object, the field, and an optional value-change condition.
Recurring Schedule	Choose Daily, Weekly, Monthly, or a custom CRON schedule and set the time. Supported objects can also use date and field filters.
Inbox — Customer message received	Starts when a contact sends a message into the Inbox.
Inbox — New conversation	Starts when an Inbox conversation is created.
Inbox — Conversation resolved	Starts when a conversation is marked resolved.
Inbox — Conversation assigned	Starts when a conversation is assigned.
Inbox — AI escalated to a human	Starts when the AI receptionist hands a conversation to a person.

Inbox triggers are entityless: they use the conversation context and do not require a CRM object selection.

Add conditions

Add Check If when the workflow should continue only for matching data. Choose the entity, field, operator, and value. Available operators depend on the field type and can include equality, text matching, number comparison, date comparison, empty-value checks, and boolean checks.

Connect the Yes and No branches deliberately. A disconnected branch will not run, and the builder's Validate action reports disconnected nodes.

Add a delay

Use Delay when a later step should wait. Configure the wait relative to the workflow context or the timing options shown by the node. For recurring work that starts independently on a timetable, use a Recurring Schedule trigger instead of treating a delay as the trigger.

Add object-specific actions

Select Do Something after choosing the trigger object. FieldCamp filters the action list so only supported actions appear for that object and context.

Group	Actions that can appear
Communication	Reply to conversation, Send SMS, Send WhatsApp, Send WhatsApp (with SMS fallback), Send Email, and Send Invoice
Assignment and status	Assign Technician, Update Job Status, Update Request Stage, Change Stage, and Update Field
Records and accounting	Create Follow-Up, Create Invoice, Sync to QuickBooks, Create Record, Create Estimate, Create Todo, and Execute Operation
AI and safeguards	AI Agent and Validate Capabilities

The exact list depends on the trigger object:

Reply to conversation is for an Inbox-triggered workflow.
Sync to QuickBooks requires the supported QuickBooks connection and a compatible object.
Send WhatsApp actions require a configured WhatsApp account; the fallback variant can send the configured SMS fallback when WhatsApp cannot deliver.
Execute Operation shows only operations registered for the selected object.
Validate Capabilities is available for supported Job and Visit workflows.

Request workflow limitation

For Request workflows, the supported action list includes messaging, Update Request Stage, Create Follow-Up, Change Stage, Update Field, Create Record, Create Todo, AI Agent, and the customer-call action.

Request workflows do not offer Assign Technician or a generic Send notification action. Use an available email, SMS, WhatsApp, follow-up, stage, record, todo, AI Agent, or call action instead.

Configure an AI Agent step

The dedicated AI Agent node is separate from a standard action node. Configure:

optional data sources;
the AI Prompt;
the AI Model; and
optional temperature.

Connect the node in the same way as other workflow steps. Its output becomes part of the tracked execution.

Validate and save

Select Validate.
Correct missing triggers, multiple triggers, or disconnected nodes.
Select Save.

The workflow must be saved once before its built-in test can run.

Run a safe test

Select Test Run in the saved workflow.
For a record-based trigger, choose Pick record and select a safe record, or choose Enter manually and provide valid JSON field values.
For an entityless trigger, confirm that no record is required.
Select Test Run to start the tracked execution.
Review the execution steps and confirm each result.

Test Run performs real actions, including SMS, email, WhatsApp, record updates, and status changes. Use a designated test record and recipients who expect the test.

If FieldCamp reports invalid JSON, correct the field values before retrying. If a run fails, inspect the failed step for missing record data, an unavailable connection, or an action that is not valid for the selected object.

Activate and monitor

Set the workflow to Active only after its validation and Test Run produce the expected result. Use My Workflows to review total runs, success rate, last run, failures, and execution details. Set it to Inactive when it should stop responding to new events.

Return to the Workflow Automation overview for the feature model and management surface.

Build and Test Workflows | FieldCamp

On this page