Work Order Block Configurator

A detection is only useful if someone goes and fixes the thing. This page configures a Custom Python Block that takes what a Workflow just saw, the annotated frame, the model's predictions and where and when it happened, and files it as a Salesforce Work Order with the evidence image attached. It works with any Roboflow model: object detection, instance segmentation, keypoints or classification.

1 Fill in your setupDestination, Salesforce org, severity, site, crew, schedule and SLA hours. The token is never part of the output.

2 Copy the block codePaste it into a Custom Python Block's code editor in the Roboflow Workflow builder. Your values are already in it.

3 Type the builder valuesThe second tab lists each block field with the exact value, plus the inputs to declare and the chips to wire.

What it looks like in the builder and in Salesforce

Roboflow Workflow builder canvas with a detection model, bounding box and label visualization blocks, the custom block, and the outputs node — The workflow: model, visualizations, then the custom block at the end.

The custom block configured in the builder with image and predictions wired as chips, destination salesforce_work_order, and severity Critical — The block configured. Image and predictions arrive as chips from the blocks above it.

Edit Custom Block panel listing the declared inputs and their types — Inputs to declare on the block. The names must match the code's parameters.

Edit Custom Block panel listing the four outputs: payload, result, error_status, message — The four outputs: the payload it built, the destination's answer, an error flag and a one-line message.

A Salesforce Work Order record with Priority Critical and a description listing severity, observed time, location, detections, requested start and due by — The result in Salesforce: subject, priority, SLA dates and the full description, with the annotated frame under Files.

Below, answer the questions on the left. The right side writes the code and the builder values. Nothing you type leaves this page.

Your setup

Destination Where should the work order go? Salesforce instance URL Salesforce API version

The access token is never part of the generated code. You pass it at run time through a workflow input named salesforce_token.

What was seen

Severity Alert type

Description (what a technician should read first) Only file a work order when at least this many detections

Where

Site name Zone / line Asset id Camera id

Street City State Postal code Country

Who and when

Crew skills (comma separated) Headcount Team

Estimated duration (hours) Parts (comma separated)

Access notes Instructions

SLA hours from "observed" to "due by", per severity

Critical High Medium Low

Salesforce fields Extra fields set on every record (JSON, API names)

Example: {"WorkTypeId": "08q...", "Source__c": "Roboflow"}. Custom fields that come from the detection itself go in the work_order_fields function in the generated code.

Attach the annotated frame to the record

Paste into the Custom Python Block's code editor. Your SLA table, destination and field settings are already filled in.