FieldCampWorkflow Automation Overview | FieldCamp
Learn how FieldCamp workflows use triggers, conditions, delays, actions, and AI Agent steps, and understand the permissions and connections they require.
Workflow Automation lets FieldCamp respond to record changes, schedules, and Inbox activity without requiring a person to repeat each step manually. A workflow can evaluate conditions, wait, send a message, update or create records, run an operation, or use an AI Agent step.
Workflow Automation is a core FieldCamp feature. It is not an add-on that must be enabled in Apps & Integrations.
Open Workflow Automation
- Open Settings.
- Under Automation, select Workflow Automation.
- Choose Templates to browse available starting points or My Workflows to create and manage your own workflows.
Administrators can manage workflows. Custom roles need the appropriate workflow builder create, edit, or delete permission under system settings. Review roles and permissions if a control is missing.
How a workflow is built
The builder palette groups steps into four areas:
| Area | Available step |
|---|---|
| Triggers | When This Happens starts the workflow. |
| Logic | Check If branches on conditions, and Delay waits before continuing. |
| Actions | Do Something performs an action supported by the selected object and connected services. |
| AI | AI Agent runs an AI prompt with selected data and model settings. |
A workflow normally begins with one trigger. You can then add conditions, delays, one or more actions, and an AI Agent step where it is useful. Follow Building Workflows for the complete setup and Test Run process.
What can start a workflow
FieldCamp exposes these trigger families:
- Record Created, Record Updated, and Record Deleted
- Status Changed and Field Changed
- Recurring Schedule
- Inbox events for a customer message, new conversation, resolved conversation, assigned conversation, or AI escalation to a human
- Call — Missed call, when an inbound call is not answered, including when the caller leaves a voicemail
Record triggers ask you to choose the object and, when applicable, a field or stage transition. A recurring trigger asks for its schedule and can optionally target records that match supported date and filter rules. Inbox triggers do not require a CRM object.
Narrow an Inbox trigger to one channel
Inbox and call triggers accept an optional channel filter: phone call, SMS, WhatsApp, Facebook Messenger, Instagram DM, email, website chat, or online-booking chat. Without a filter the workflow fires on every channel, so a missed-call follow-up would also chase someone who simply sent their first text. Set the filter whenever the automation only makes sense for one channel.
A missed call and a voicemail arrive on the same trigger. Use the isVoicemail value in a condition when the two need different messages.
What a workflow can do
The action picker changes with the selected object and trigger. Depending on that context, actions can include:
- Send Email, Send SMS, Send WhatsApp, or Send WhatsApp with SMS fallback
- Reply to the triggering Inbox conversation
- Assign Technician, Update Job Status, Update Request Stage, Change Stage, or Update Field
- Create Follow-Up, Create Invoice, Send Invoice, Sync to QuickBooks, Create Record, Create Estimate, or Create Todo
- Execute Operation, AI Agent, or Validate Capabilities
Operations reachable through Execute Operation include linking a job to a custom-object record and renewing a contract, which is what the automation recipes provision for you. Message actions can also insert the visit's arrival window, so a reminder quotes the promised window instead of an exact time.
An action appears only where FieldCamp supports it. Messaging and accounting actions also require the corresponding sending number, WhatsApp account, mailbox, or accounting connection.
Do not assume that an action available for Jobs is also available for Requests, Clients, or Invoices. Select the trigger object first, then use the action list FieldCamp shows for that object.
Use templates or build from scratch
The Templates tab provides preconfigured workflow structures. Open a template to review its requirements and preview its nodes before selecting Use This Template.
The My Workflows tab lists saved workflows and shows their status and run statistics. Select Create New Workflow to open a blank builder, or use workflow templates when a supported template already matches the job.
Use workflow examples for evidence-backed patterns that respect the object-specific action lists.
Test before activation
The builder includes Test Run. A test can use a selected record or manually entered JSON field values, depending on the trigger. Entityless triggers, such as Inbox activity, do not require a record.
A Test Run performs real actions, including messages and record changes. Use a designated test record and safe recipients.
Save the workflow once before testing. After the run starts, review its tracked execution and confirm every step produced the expected result before setting the workflow to Active.
Monitor workflows
The workflow dashboard can show:
- Total Workflows and Active Workflows
- Total Executions and Success Rate
- per-workflow run totals, failures, average duration, and last run
- execution details and step data for individual runs
If a workflow fails, inspect the execution rather than retrying blindly. Correct the missing data, connection, or action configuration first.
Related articles
Workspace Views | FieldCamp
Pin and organize FieldCamp modules in your sidebar to build a personalized workspace. Quick-access the tools you use most without navigating through menus.
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.