Release notes

Text inputs and variables now offer Speech and keypad and Keypad only in their Voice capture settings. This applies to Action inputs and to Playbook Ask steps.

Use a Text input for digit strings that can start with 0, such as the last four digits of a card, an expiration date, or a one-time code. A Number input drops leading zeros, so “0430” is saved as 430.

Availability rules on knowledge sources shipped over the last two weeks for web import sources, Knowledge API sources and the sources that an Ada App creates. This note covers the changes that came with that work and have no release note of their own.

Rename and delete a Knowledge API source from the dashboard

The Settings window of a Knowledge API source now holds more than its availability rules.

• Source name: rename a source that you created through the Knowledge API. No source can take the name Created in Ada.
• Delete source: delete the source and all of its articles, with the same confirmation as a web import source.

Open the window from the Sources tab with the Settings button beside the source. See Connect through the Knowledge API.

200 articles per page

The article list on the Knowledge page can now show up to 200 articles per page. The largest page size was 100. Bulk actions such as Set as inactive and Set availability apply to every selected article on the page. A cleanup of thousands of articles takes half as many pages. See Article management.

Knowledge sources over the MCP server

edit_agent_config and list_entities now cover source settings and availability rules.

• edit_agent_config with entity_type='knowledge_source' accepts availability_rules on create, creates a website import when the request passes start_urls and an optional sync_frequency, and offers a new update operation. Depending on the source type, update changes the name, the sync frequency or the availability rules.
• list_entities with entity_type='knowledge_sources' returns each source’s availability_rules at full detail.
• list_entities with entity_type='variables' lists every variable that an availability rule can reference, including channel, chatter_id and end_user_id and the sensitive and sensitive_meta scopes, so an assistant can find the variable ID a rule needs.

Playbooks now have a NOTE step. AI Managers can record the intent of a flow next to the steps it explains. For example, a note can say why a branch exists or what the values of a variable mean.

What’s new

A NOTE step is an annotation for the people who edit the Playbook.

• Never runs. The AI Agent skips notes, and end users never see them.
• Goes anywhere. Add a note between any two steps, including inside an IF/ELSE branch. Drag it like any other step.
• Shows its author. The note header shows who last edited the note and when.
• Keeps step numbers. A note takes no line number, so the steps around it keep their numbers.

To add a note, select NOTE in the add-step menu.

See NOTE.