Automation recipes and renewals | FieldCamp

Apply a FieldCamp automation recipe to a custom object to auto-extend recurring work, invoice for activation, and send customers a one-tap renew link.

An automation recipe is a ready-made automation you attach to a custom object. Applying one provisions the workflows it needs and adds the matching buttons to the record page, so a Contract, Membership or Agreement object starts behaving like a product feature instead of a spreadsheet.

Recipes are generic. Any custom object can adopt any recipe.

Before you begin

Only account administrators can change an object's automation.
The object should already have its stages configured, because most recipes ask which stage to move a record into.
For renewals, the object's records need to be linked to the recurring jobs they cover. See Link custom objects to the pipeline.
For paid activation and paid renewals, connect Stripe first. See Connect Stripe.

Apply a recipe

Open Settings > Custom Objects and select the object.
Find the Automation Recipe card.
Choose a recipe from the list. Nothing is provisioned yet — the card switches to a review step.
Fill in the recipe's configuration.
Select Apply.

FieldCamp then creates the recipe's workflows and adds its record actions to the object's detail page. Applying the same recipe again does not duplicate anything.

Workflows created by a recipe start in Draft. Open Workflow Automation, read the message copy and the details, then activate them. Until you do, no customer receives anything.

Choosing None clears the recipe and removes its record actions. The shared workflow is only paused when no other object still uses it.

The recipes

Recipe	What it does
Renewal (recurring service)	Auto-extends visits on recurring jobs before they run out, and adds a Renew Now button to the record
Paid activation (invoice-gated)	Adds a Create Dues Invoice button; when that invoice is paid the record moves to your active stage automatically, by card or by cash and check
Renewal + paid activation	Both of the above
Customer renew link (contracts and memberships)	Reminds the customer before their contract ends and lets them renew in one tap from a link, with or without payment

Configure paid activation

Setting	What it controls
Stage after payment	Where the record moves once its invoice is paid
Stamp payment date into	An optional date field that records when payment landed
Invoice lines from	Record's amount field for a manual price, or Covered job's line items for real prices and taxes
Invoice amount field	The field to read when invoicing from the record's amount
Payment terms (days)	The due date offset on the generated invoice

Configure the customer renew link

Setting	What it controls
Renewal mode	Share renew link — customer pays online, Share renew link — free, no payment, or Office only (staff renews)
Reminder days before last visit	When reminders go out, for example `30, 7`
Reminder channel	Email + SMS, SMS only, or WhatsApp (auto SMS fallback)
WhatsApp template	Optional. Left empty, FieldCamp auto-detects the template tagged Contract Renewal
Don't renew if series ended more than N days ago	A safety cut-off for stale contracts

Online payment charges the covered job's line-items total.

What the customer sees

The reminder carries a one-tap renew link. Opening it shows the renewal, takes payment when the mode requires it, and completes the renewal on the spot. Renewal extends the same job by its own repeat schedule and creates the next-period record, so history stays on one thread instead of splitting into a new job each term.

If the customer pays the dues invoice but never clicks the link, a safety-net workflow completes the renewal from the payment. It is idempotent, so a contract is never renewed twice.

Renew from the office

Administrators, dispatchers and the workspace owner can always renew by hand with the Renew Now action on the record — even when the customer link is turned off.

Automation recipes and renewals | FieldCamp

On this page