Configure Procedures and Actions

Create a Procedure

Open Settings > AI > Procedures and choose a template or create a Procedure from the supported action registry. Keep the trigger, Inbox or audience and action scope explicit.

Save a draft first. Drafts do not run and do not change an existing published version.

Run a dry test before publishing

• Choose a synthetic or already safe Conversation in the Procedure test panel.
• Check every condition, planned action and approval result. A dry test does not send a customer message or execute a provider mutation.
• Fix missing Inbox targets, invalid conditions or safety blocks, then run the test again until the expected result is shown.

Shape and test a Custom API result

After a successful safe test of an enabled GET read operation, open Edit operation and go to Response. The guided result layout turns mapped typed output into a customer-readable single record or record list. Only safe record candidates from the tested response are offered.

Set a result label in every supported language, choose a title and optional subtitle field, select up to 32 safe fields and set the maximum number of records for a list. Preview the result in each language before saving. Amounts, dates and statuses use their typed display rules. Unknown statuses and missing fields stay unavailable instead of being guessed.

1. 1

   Use the read-operation Test action with safe test inputs. The parsed response shows typed fields, nested paths and hidden sensitive values.

2. 2

   Choose Edit operation > Response, select Single record or Record list, then set the result label, title, optional subtitle and visible fields. For a list, set a maximum of 1 to 100 records.

3. 3

   Review the localized preview, choose Use this layout and then Save as draft. Advanced response remains a bounded technical JSON preview. It is not an editable request and it does not run a mutation.

• Customer displays support text, number, yes or no, amount, date and status fields from the mapped response.
• Record lists are bounded to 100 records and 32 fields. The interface shows a partial warning when the provider returns only part of the result.
• If the response is empty, malformed or a field is unavailable, show unavailable and fix the response mapping or hand off instead of guessing.

Guard a Custom API change

For a customer-confirmed Custom API change, optionally add a mutation condition. It can read only a string output and compares it with the exact expected value. A missing, mismatched or unavailable value routes to a human handoff and does not call the mutation.

Every external change still requires customer confirmation. Protected or sensitive changes always need teammate approval. A read test never bypasses these safeguards.

Publish and verify the runtime result

Publish only after the dry test is understood. A published Procedure is versioned. Later drafts do not replace the active version until you publish them.

Trigger one controlled runtime test and confirm the completed run in the Procedure history. Setup Center uses that successful run as evidence that the published action is executable, not merely saved.

Billing, account, privacy, legal, security, abuse and angry-customer actions keep their approval or human handoff requirement. Never weaken that policy to make a test pass.