FieldCamp

Agents in Workflows | FieldCamp

Use AI agents as intelligent steps inside FieldCamp workflow automations. Combine triggers and conditions with AI-powered actions for smarter business processes.

FieldCamp's workflow automations let you set up triggers, conditions, and actions that run automatically. Adding an AI Agent as one of those actions makes your workflows smarter — instead of just sending a templated email, the agent can draft a personalized message, decide what to say based on context, or handle a conversation.

What It Means

A regular workflow action is fixed: "send this email template" or "change the status to Complete." An AI Agent action is intelligent: "look at this job, figure out the right follow-up message, and draft it." The agent brings reasoning and personalization to your automations.

How to Add an Agent to a Workflow

  1. Go to Settings > Workflow Automation or open the Workflow Builder
  2. Create a new workflow or edit an existing one
  3. Set your trigger (the event that starts the workflow, like "Job completed")
  4. Add any conditions you need (like "Only if job value is over $200")
  5. For the action step, drag the AI Agent node onto the canvas
  6. Select which agent should run from the dropdown
  7. Configure what data gets passed to the agent (client name, job details, invoice amount, etc.)
  8. Save and activate the workflow

When the trigger fires and conditions are met, the selected agent runs its task with the data you pass in.

Real-World Examples

Follow-Up Email After Job Completion

Trigger: A job status changes to "Completed"

Condition: The job value is over $200

AI Agent action: The Follow-Up Agent reviews the job details, drafts a personalized thank-you email mentioning the specific service performed, and includes a link to leave a review.

Next action: The Send Email action delivers the agent's draft to the client.

Without the agent, you would send the same generic "Thank you for your business" email to every client. With the agent, each email references the actual work done and feels personal.

Appointment Confirmation Call

Trigger: A visit is scheduled for tomorrow

AI Agent action: The Appointment Scheduler agent calls the client, confirms the date and time, and asks if they have any questions or special requests.

Result: Fewer no-shows because every client gets a personal confirmation call the day before.

Overdue Invoice Escalation

Trigger: An invoice is 14 days past due

Condition: No payment has been recorded

AI Agent action: The Invoice Reminder agent sends a polite but firm email with the outstanding amount, due date, and payment link.

Next action: If still unpaid after 7 more days, a second workflow triggers the agent to make a phone call instead.

New Request Triage

Trigger: A new request is created

AI Agent action: A triage agent reads the request description, categorizes it by urgency and service type, and adds internal notes with a recommended priority level.

Next action: The workflow assigns the request to the appropriate team member based on the agent's categorization.

What Data Can You Pass to the Agent?

When you configure the AI Agent node in the workflow builder, you choose which fields from the trigger event are passed to the agent. Common fields include:

DataUse Case
Client name and contact infoPersonalize emails and calls
Job or visit detailsReference specific work performed
Invoice amount and due datePayment reminders and follow-ups
Request descriptionTriage and categorization
Technician nameInclude in client communications
Scheduled date and timeAppointment confirmations

The agent uses this data along with its instructions and connections to complete its task.

Tips for Agents in Workflows

  • Keep the agent focused — the workflow handles the trigger and conditions, so the agent only needs to handle its one action
  • Test the agent separately first — make sure it works in the Agent Chat before adding it to a workflow
  • Chain agents with other actions — an agent can draft a message, and a separate Send Email action can deliver it. This lets you review agent outputs before they go out if needed
  • Monitor execution history — check the workflow dashboard to see how often the agent runs and whether it succeeds

The agent must be set to Active status for it to run inside a workflow. If the agent is Paused or in Draft, the workflow will skip that step.

Start with a simple combination: trigger on job completion, have the agent draft a personalized follow-up email, and send it automatically. Once you see how it works, build more complex flows.

Next Steps

On this page