Set Up Driver Actions
  • 14 Jun 2023
  • 19 Minutes to read
  • Dark

Set Up Driver Actions

  • Dark

Article Summary

Driver actions are the stages in an order flow which a driver performs in the Bringg Driver App to complete the fulfillment of that order. You can set up mandatory and optional actions to prompt drivers to take a payment, obtain the customer's signature, take a photo, fill out a form, open a webpage, and scan a barcode to confirm a handoff.

The Bringg Driver App can prompt drivers to perform driver actions for any order, or only those which have certain types of goods. It can suggest to perform these actions at the start of a shift, at the end, or during handoff (after check in or before checkout).

Create driver actions to guide drivers through the fulfillment process 

You can add variations to your order flows using service plans in order to offer consumers different levels of service. For example, a basic plan may assign default delivery slots, while over the threshold plans may offer consumers faster fulfillment, or the option to choose a specific arrival date or time.

Before You Begin

  • Define order flows for each type of order and eventuality, including the steps which are optional vs. mandatory.
  • Add drivers to Bringg and ensure they use the Bringg Driver App. Learn more.
  • Define the permissions of drivers on the Driver App in Settings > Driver App > Configuration.


Step 1: Access the driver action flows by selecting Settings > Driver App > Actions Configuration.

Access the driver actions page


Step 2: To create a new flow of driver actions, select Create new action configuration or select Edit on an existing flow.

Create a new driver action flow


Step 3: Name your flow to make it easy to find and recognize.

Name your flow


Step 4: Define if this order flow applies to all orders, certain types of orders, or specific types of good or services.

Define the scope of your flow




Particular Orders

Use this level for actions on the order level, for example to prompt drivers to take payment for orders that consumers pay for using cash.


Use this level for actions that apply for specific inventory, such as extra precautions for flammable materials.

All Shifts

Use this level to create actions that drivers complete when beginning or ending their shifts.

Step 5: To add a driver action to the flow for this type of order, create a new driver action by selecting Add New Action.

Your flow can contain as many driver actions as required.

Create a driver action





Select this option when an order can follow different flows. Depending on the answer to a question, you can define a different path in the flow of driver actions.

Enter a question as free text in any supported language which the Driver App displays. For example, was the customer at home? Do they have ice bags to return? How many?

Add as many predefined answers as needed, by selecting Add Answer.

When the driver selects an answer, you can define the next driver action by selecting Go to and choosing the title of the next action.

Action form

Select to define a form which the driver can fill. You can define each field in the form, its label, the type of input, and potential values. For example, you can also add to collect a photo or signature as part of a form. For details, see the step about action forms.

Reject inventory

(Only for flows applying to specific goods or services) Select to update Bringg that the customer or driver rejected one of the goods or services in the order, perhaps because they are not needed, damaged, and so on. The Driver App displays a list of predefined reasons. To customize, contact your Bringg customer service representative.

Take note

Select to allow the driver to add a note to the order in plain text, which remains stored with the order. You can view it later in the order details .

Verify customer  pin codeSelect to require the driver to enter the 4-digit pin code the customer receives in order to confirm fulfillment of the order.

Take signature

Select to insert a customer signature into the flow. In the Driver App, you can add a signature by drawing it with your finger on the mobile device. Use signatures to confirm the customer took custody of an item, or rejected an item, or any other reason which requires a proof of consent.

To add text to the signature screen, enter it in the Disclaimer field.

To allow drivers to share the signature with the customer in the customer experience page, select show share with customer checkbox and choose whether you want to share by default.

Take picture

Select to insert a driver action to add a photo to prove handoff, or record any damage. You can use the device's camera to capture the image and you can view it later in the order details .

To allow drivers to share the photo with the customer in the customer experience page, select show share with customer checkbox and choose whether you want to share by default.


Bringg stores photos for 90 days inside the order. You can transfer it to another system via a webhook, which creates a temporary URL for the system to access the image, which is valid for six days.

Take scan

Insert a driver action to scan a barcode or QR code with the camera, to prove that a handoff occurred in the chain of custody. This is typically at the start of a shift.

Cancel task

Select to allow the driver to cancel an order. The Driver App displays a list of predefined reasons. To customize, go to Settings > Merchant Configuration > Cancellation Flow.

Open webpage

You can extend the Driver App with your own add-on functionality by linking it to any external webpage. For example, you can link to a page which processes credit card payments with the appropriate hardware, or fill a form which checks the price of adding an extra service.

For details, see the step below about external webpages.

Step 6: Add more conditions when a driver can perform this action.

The Driver App only offers this action if all conditions are met (AND relationship).

Add further conditions when to display an action




Waypoint type

Select to only offer this action for certain types of destinations:

  • All offers this action at any type of destination.
  • First only offers this action at the first destination of an order. To specify only for pickups, use Task type.
  • Customer only offers this action when at the customer's location.
  • Last only offers this action at the second destination of an order.
  • Warehouse indicates to offer this action only at the fulfillment center.

Task type

Select to only offer this action during Pickup, Delivery or Return. To restrict this to a destination which has both a delivery and a pickup, select Pickup and Delivery.

Show on actions menu

To display this action in the list of driver actions when you tap the + button when you arrive at a destination, select True.

When to execute

To run this flow automatically, without needing to tap +, select:

  • Allowed indicates it's optional and available at any time.
  • After checkin indicates that this action is optional, but you can only perform it after at the destination.
  • Before checkout indicates that this action is a mandatory prerequisite to checking out.

If you mark a step as mandatory, the flow cannot proceed until the driver starts and completes this step. For example, you may define a separate flow for prescription medicines to require a signature at handoff.

  • Default Not in use.
  • Un-allowed Not in use.
  • Before start tasks indicates it's a mandatory action before you tap Start Pickup/Dropff for this order.

When to show

Not in use.

Show share with customer checkbox

(Signatures and photos only) Select to display the option to the driver to share the signature or photo with the customer in the customer experience page.

Step 7: (Forms only) If you want the driver to complete a form, add each field with its labels and details by selecting Choose action > Action form > Add new component and expanding (Field).

Select the type of form element you want to add in Visual Element.

Define fields of the custom form





Select to add a field in the form. Define:

  • Label is the title of this field in the form.
  • Format determines whether the field is plain text, numeric or a true / false choice.
  • Key is the internal ID of this field, which you might need when using a webhook to pass the value of this field to another system.


Select to add a checkbox and enter its label.


Select to insert a toggle and enter its label.


Select to add a dropdown menu of choices. Select Add dropdown value to insert choices.


Insert a place in the form which allows for a signature for consent.


Insert a place in the form where the driver can add a photo (take new or select existing).


Insert to display general guidance text for the driver, not requiring specific input.


Select to display your company logo at the top of the form. It uses the logo stored in Settings > Tags.

Step 8: (External webpages only) To insert any addon functionality into a driver action, like payment processing, point to a webpage by selecting Open webpage.

You can send data about the order to the webpage as URL parameters, and return an indication of the functionality’s success when you close the page.

In URL, enter the web address, where you can choose the parameter names, but the placeholder values must have specific names:

  • #task_id is Bringg’s internal ID of the order.
  • #external_task_id is your ID of the order.
  • #way_point_id is the Bringg ID of the destination for this order.

Add the following JavaScript functions to your webpage, which you design for mobile screen sizes:

  • BringgDriverAppCompleteAction() indicates the action in this webpage completed successfully.
  • BringgDriverAppCloseIframe() closes the webpage (no taps needed) and returns to the Driver App.

Select Must complete successfully > Yes if the order flow cannot proceed to the next step until the driver completes it successfully.

Here is an example of a webpage with these function calls:

<form onsubmit="return back2App()">
  // form fields

   window.onload = function() {
        let urlParams = new URLSearchParams(;
        let orderid = urlParams.get('taskID');
        document.getElementById("taskID").innerText = orderId

   function back2App() {
        return false;
   function BringgDriverAppCompleteAction() {
    if ("webkit" in window) {
        // iOS callback
    } else {
        // Android callback

   function BringgDriverAppCloseIframe() {
    if ("webkit" in window) {
        // iOS callback
    } else {
        // Android callback


Step 9: (Optional) To automatically add a specific amount of time to the estimated time on site (ETOS) for orders that use this flow, contact your Bringg customer service representative to request a time on site buffer.

For example, you can add an automatic buffer of 15 minutes for orders with a service plan that requires your driver to install a product in a customer's home.

Step 10: Select Save to save the flow and assign it an ID. You can then use this ID to assign the flow to specific orders and inventory.

Use the flow's ID to assign it to orders


  • To assign a flow to a specific service plan, go to Settings > Merchant Configuration > SERVICE PLANS, select > Edit, and choose the flow from the Task configuration list. Learn more.
    Add your flow to a service plan


  • To assign a flow to certain types of orders, ask your IT integrator to add this ID to the task_configuration_id in the payload at the task level.
  • With your IT integrator, assign a flow to orders with certain goods or services, add this ID to the actions_configuration_id in the payload at the inventory level.

Was this article helpful?