Create a mission that returns a small synthetic bill-review message without calling an external app. This walkthrough uses Data Mapper, so you can learn the builder before configuring provider accounts or a custom-code runtime.

​
Create the mission

  1. Open Missions in the intended Command Center.
  2. Choose Create New, then New Mission.
  3. Double-click the mission name at the top, enter Practice bill review message, and press Enter.
  4. Select the trigger node, search for Manual Trigger, and choose its action.
Manual Trigger passes an empty object. It does not provide a bill ID to later steps. Add the sample values in the mapping action below.

​
Add the mapping step

Use the plus control below the trigger. Search for Data Mapper and select Advanced Mapping. Replace the default Mapping object with:
Keep these literal values for the first test. This built-in action requires no provider account and does not send a message.

​
Test and inspect

Wait for the edit to finish saving, then choose Test Step. Open Output and confirm both fields match the JSON above.
Fresh Data Mapper test returning BILL-DEMO-001 and its review message
The test above was executed in the renamed development app on 7 October 2026 using this exact object.

​
Publish and run

Choose Publish. In the tested build, publication enables this manual-trigger mission and displays Run Mission on the canvas. Confirm the enable switch and use Run Mission to invoke it. A manual trigger waits for invocation; enabling it does not schedule runs. Select the mapping step in the completed run and inspect Output. Open Run history and select the recorded invocation to confirm the result was saved.
Fresh published mission run succeeded and returned the documented bill-review object
This run was executed after publication on 7 October 2026. It is the practice mission’s actual result, not an older Hello world example.

​
Add a mapped step later

Add another action after Advanced Mapping and choose bill_id or message from its output in the data selector. See passing data. Use test accounts and destinations when adding a send, write or delete action; testing it can affect the connected app before publication.

​
Custom Code prerequisite

A Code step is a separate option requiring its supported sandbox runtime. If it fails with AP_DENO_PATH is not set, ask your operator to configure the Deno binary for the selected release. The built-in mapping walkthrough above does not need custom Code. See feature availability.