Create and Configure AI Agents | FieldCamp

FieldCamp agents combine instructions, an AI model, connected tools, a trigger, and notification settings. Start with the AI agents overview if you first want to understand where agents fit in FieldCamp.

Create an agent

1. Open Agents from the main navigation.
2. Select the option to create an agent.
3. Describe what the agent should do, choose a template, or select Or create empty.
4. Review the proposed configuration before continuing.
5. Complete the agent details, model, trigger, connections, and notifications.
6. Select Create & Activate Agent when the configuration is ready to run.

Configure the agent details

The Agent Details section contains:

• Name — a clear label your team can recognize.
• Description — a short explanation of the agent's purpose.
• Instructions — the task, rules, tone, and boundaries the agent should follow.

Write instructions that say what the agent should do, what information it may use, when it should stop, and what it must not do. Keep one primary responsibility per agent when possible.

Choose an AI model

The current model choices are:

• Claude Sonnet 4
• Claude Haiku 4.5
• GPT-4o
• GPT-4o Mini

Choose the model based on the complexity and speed required by the task, then test the agent's output with safe records before relying on it for customer-facing work.

Choose how the agent starts

The Trigger section offers four modes:

Configure a scheduled trigger

1. Select Schedule.
2. Under Frequency, choose Daily, Weekdays, Weekly, or Monthly.
3. Set the Time.
4. Review notification recipients. Manual and scheduled runs do not have a triggering customer or assigned technician, so those recipient choices are unavailable.

Configure a FieldCamp event trigger

1. Select Event.
2. Under Listen to event, choose the FieldCamp event that should start the agent.
3. If FieldCamp shows Requires connection, connect the named service before activating the agent. Use agent connections to prepare the required data source or integration.
4. For a stage- or status-transition event, optionally choose From stage and To stage. Leaving either selection empty means Any stage for that side of the transition.
5. Choose notification recipients that make sense for the triggering record.

Event-triggered runs can use the customer or assigned technician from the triggering record. If you later change the trigger to Manual or Schedule, review those recipients because the run no longer has that record context.

Configure an API trigger

Select API when another application should start the agent. The trigger is intended for a POST request from your code. Keep the caller on a trusted server, restrict its FieldCamp access, and do not embed credentials in browser code.

Select connections

Connections are the data sources and integrations the agent can access. FieldCamp Data is always included. Other connections show whether they are Connected or Not connected and how many tools they provide.

Only select connections required by the instructions. A trigger can also require a specific connection; FieldCamp shows that requirement below the selected event.

Configure notifications

Choose how FieldCamp should notify people after an agent run:

• In-app — show a notification in FieldCamp.
• Email — send a summary email and optionally attach a PDF, CSV, or Excel report.
• SMS — send the agent's message through a connected Twilio number.
• WhatsApp — send through the connected WhatsApp account.

Customer and assigned-technician recipients are available only for Event triggers because those runs have a triggering record. For SMS and WhatsApp, confirm the required sending account is connected before activation.

Edit an existing agent

1. Open the agent and select its configuration page.
2. Use the section navigation to review Agent Details, Model, Trigger, Connections, and Notifications.
3. Make the required changes.
4. Select Save Changes.

FieldCamp keeps configuration versions after saves. Use Version history to inspect a previous version or restore it when you need to undo a configuration change.

Review before activation

• Confirm the trigger matches the intended start condition.
• For Schedule triggers, verify the frequency and time.
• For Event triggers, verify the event, connection, and any From stage or To stage filters.
• Confirm every selected connection is necessary.
• Check all notification channels and recipients.
• Use safe test data before allowing the agent to contact customers or change records.

If configuration controls are missing, compare your access with FieldCamp roles and permissions.

Related articles

• Use agents in workflows
• Set up voice agents