Skip to content
Explore integrations

VH3 AI integration researchA little less busywork with VH3 AI.

Research only. Grunt is prelaunch, live service is paused, and live provider connections and outcomes remain unverified. The operations and examples below are not confirmed live Grunt features or approved supplier commitments.

Explore possible VH3 AI workflows with Grunt. Documented operations include Job (BigChange): Cancel a job; Job (BigChange): Create a job; Job (BigChange): Create a job with dynamic custom fields. Actions on this page are research candidates from public integration definitions, not confirmation that Grunt support is live.

Exploratory scope only: these candidates come from public integration definitions and are not confirmed as live Grunt features.

VH3 AI
“Explore whether a Grunt integration could cancel a job, then create a job in VH3 AI. Show me the result and wait for my approval before changing anything.”
A workflow idea to explore.

Illustrative steps and outcome; no real work is performed here.

  1. 01Job (BigChange): Cancel a job
  2. 02Job (BigChange): Create a job
  3. 03Review the result before anything changes

A clearer next step, with the final say still yours.

Explore possibilities with VH3 AI.

Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.

225 researched capabilities across 38 groups

  • Cancel a job

    Cancel a field service job. Requires the numeric job ID. Optional reason text. Use only when the job will not happen at all (otherwise prefer Set Job Result with completedWithIssues).

  • Create a job

    Create a new field service job. Requires a job type ID (from List Job Types) and a contact (customer/site) ID (from List Contacts). Returns the new job ID. Does not schedule it — call Schedule Job afterwards.

  • Create a job with dynamic custom fields

    Create a job where custom fields are supplied as a pre-built JSON array from a previous node (e.g. a Code node). Useful for automated pipelines where custom field values are resolved dynamically at runtime rather than configured manually.

  • Create a job constraint

    Add a scheduling rule to a job (e.g. must start before X, requires engineer Y or skill Z). Time-based types need constraintAt; resource/skill types need entityId. Used by the BigChange scheduler.

  • Create job stock entry

    Plan or record stock/parts movement on a job (brought, used, taken back). Requires job ID; supply stockDetailsId or stockItemId plus an action and quantity.

  • Delete a job constraint

    Remove a scheduling constraint by its constraint ID (get it first via List Job Constraints)

  • Edit a job

    Update fields on an existing job (description, reference, planned duration, person, order number, custom fields, office notes, isActioned, isFinanciallyComplete). Does not change schedule or status — use Schedule Job / Start Job / Set Job Result for those.

  • Get an enriched job

    Get the FULL enriched view of one job (status history, assigned engineer, site address, custom fields, completed worksheet answers, attachments). Heavier payload — use this when an agent needs to summarise/answer questions about a specific job. For a quick lookup, use Get Job by ID instead.

  • Get a job by id

    Lightweight single-job lookup by numeric ID via the proxy. Optionally include worksheets. Faster and cheaper than Get Job — prefer this when you only need core job fields. Set Simplify=true to strip the deep BigChange envelope.

  • List job constraints

    List all scheduling constraints currently attached to a job (pre-existing rules the scheduler must respect)

  • List job status history

    Get the full audit trail of status transitions for a job (new → scheduled → started → completedOk, etc.) with timestamps and actors. Use to debug "why is this job in this state?" or build a timeline.

  • List job stock

    List every stock/parts line attached to a job — what was planned, brought, used, or taken back

  • List or search jobs

    Primary search for jobs. REQUIRES a created-from / created-to UTC window. Filter by status (e.g. completedOk, scheduled, started), job type IDs, contact (customer/site) IDs, resource (engineer) IDs, vehicle IDs, or reference. Returns paginated job records. Default returnAll=false. Set Simplify=true to strip envelopes.

  • Schedule a job

    Assign an engineer (resource), vehicle, and/or planned start time to a job. Use after Create Job or to reassign. plannedStartAt is UTC ISO-8601.

  • Set job result

    Close a job by writing its completion outcome. Status MUST be completedOk or completedWithIssues. Optional result text and an override timestamp. After this call the job is treated as done.

  • Start a job

    Mark a job as started (engineer en-route/on-site). Optional comment (max 250 chars) and override timestamp. Cannot start an already-completed or cancelled job.

Proposed setup considerations

The research notes below describe a possible setup. They are not instructions for an available Grunt connection; actual steps depend on supported operations and provider approval.

  1. 01

    Start with a small, useful task.

    Describe a routine step involving VH3 AI. Keep a first version easy to review and change.

  2. 02

    Plan the account access.

    Check which VH3 AI account, data, and permissions a safe connection would need. Start with the least access that can do the job.

  3. 03

    Test the details together.

    Validate a sample against a disposable account. Confirm which records are read, what could change, and how errors or duplicates are handled.

  4. 04

    Keep the say-so.

    Decide which steps could run on their own and which would need your review. Expand access only when the workflow needs it.

RESEARCH NOTES

Questions about the concept.

These notes describe possible uses. Customer availability remains unverified.

What could a Grunt integration do with VH3 AI?

The documented operations include Job (BigChange): Cancel a job; Job (BigChange): Create a job; Job (BigChange): Create a job with dynamic custom fields; Job (BigChange): Create a job constraint. These are research candidates from public integration definitions and need validation and Grunt implementation before they can be treated as supported capabilities.

Could I keep a workflow read-only?

The research candidates do not confirm an implemented VH3 AI connection or a read-only access mode. If built, verify least-privilege scopes and reject writes at the app API boundary.

Will every action run automatically?

If a connection is built, choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in VH3 AI?

A future integration should let you decide which work could run on its own and which steps need your review.

There’s a Grunt for that

A little less busywork.
A little more you.

Read the current prelaunch status and confirmed prices.

View pricing status Explore the simulation