Recipes — guided flows in chat | FieldCamp

A recipe turns repeat field work — an inspection, a checklist, a takeoff — into a guided form your team fills in chat. You describe the flow in plain language, AI builds the pages and questions, you publish it as a slash command, and every completed run creates a record.

Recipes live in Recipes (Recipe Studio). They are separate from job forms: a job form is attached to a job and completed on site, while a recipe is a command anyone can run in chat and can even be shared as a public link.

Before you begin

• Recipes are administrator-only. The Recipes pages are restricted to admin roles.
• Building or editing with AI consumes AI credits. See AI usage.
• Decide what each run should produce before you publish — the submit action is part of the recipe.

Open Recipes

From the Command Centre chat header, select the Recipes pill, or open the … menu and select Recipes.

The list shows every recipe with its status (Published, Draft, Archived), version, records created, and last run. Filter by status, search by name or command, and use Showing x of y recipes to confirm what the filter is hiding.

Create a recipe

You have three starting points.

Describe it and let AI build it

1. Select Create recipe.
2. Describe the on-site flow in the box — for example "A window inspection — count the glass in every room, price it at a flat rate per unit, get the client's approval, then measure each opening for the supplier order".
3. Optionally set a Field limit to cap the total number of fields.
4. Select Generate recipe.

Generation takes roughly ten seconds and shows its progress: reading your description, structuring steps, adding fields, validating against the spec. The live phone preview shows the exact card your team will fill.

Start from the library

Open the Recipe library for ready-made recipes grouped by trade — HVAC, Plumbing, Electrical, Cleaning, Safety, Pest control, Fleet and vehicles, Landscaping. Select Use this recipe to copy one into your workspace, then edit it.

Build it by hand

Create a recipe and edit it directly. Every recipe needs at least one page, and every page needs at least one question.

Edit a recipe

The editor has the structure on the left, a live preview on the right, and an AI Assistant panel you can talk to.

• Add pages with Add page, and questions with Add question. Reorder with Move up and Move down.
• Question types: Text, Number, Dropdown, Checkbox, Date, Time, Phone, Address. A dropdown needs at least one option.
• Mark a question Required when the submit action depends on it.
• Ask the assistant for changes in plain language — "add a photo step", "make the meter reading required" — and it lists exactly what it changed.
• Switch the preview between Mobile and Desktop.

Edits save automatically. Discard draft deletes the draft without touching the published version.

Set the chat command

The Chat command is what your team types, in the form /window-inspection — lowercase letters, numbers and hyphens. Each command must be unique; if it is taken, the editor names the recipe holding it.

Choose what submitting creates

Set the Submit button action to one of: Create request, Create job, Create estimate, Create invoice, Create client, Create product, Create service, Create custom record, or Submit only.

For Create custom record, choose the custom object and map each object field to a recipe question. Required object fields must be mapped before you can publish, and Suggest mappings does the obvious ones for you.

Publish, version and archive

1. Select Publish. The recipe goes live as v1 and the command starts working in chat immediately.
2. Later edits create a draft. The list marks it Unpublished changes while the published version keeps running.
3. Publishing again creates the next version. The Versions tab lists each one with its date, author, run count and a Preview that never submits.

Archive removes the command from chat; runs already in progress finish on their pinned version. Restore brings it back. Delete removes the recipe and all its versions permanently — records created by past runs are kept — and is blocked while someone is filling it.

Run a recipe in chat

Type the command in the Command Centre, or select Run in chat from the recipe's actions. The recipe appears as a card that steps through its pages with Previous and Next, then a submit button labelled for its action, such as Create request. When the run completes, the confirmation links straight to the record that was created.

The Runs tab on a recipe shows who filled it, the status (Complete, Running, Cancelled), the version used, how long it took, and links to both the record and the chat thread.

Share a recipe outside FieldCamp

From the recipe's actions menu:

Related articles

• Command Centre — AI chat
• AI skills — chat commands
• AI usage — balance, purchases and activity
• Job forms and checklists
• Creating and tracking requests