(Actions) Conversational AI #31390
Open
(Actions) Conversational AI #31390
+25
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview links (active after the
|
OliviaShoup
added
under_review
barakshush
reviewed
Oct 24, 2025
| - `Display a list of lambda functions in a table. Allow the user to filter by function name and specify the limit.` | ||
| - `Provide a list of PagerDuty services and their status in a table. Include a search input above the table.` | ||
| - `Display GitHub pull requests in a table.` | ||
| 1. After Bits AI responds to your prompt, you can click **Edit with AI** or manually [customize your app][15]. |
There was a problem hiding this comment.
Before that, can you add the following steps:
- Explain that the agent will will auto-generate the UI, actions, and logic, mapped to the customer's existing data and permissions.
- explain about the step where the agent ask the user User to set up a connection to build the app with real data or skip and build the app layout faster without data
- Mention that in some cases, the agent will ask clarification questions.
| - `Provide a list of PagerDuty services and their status in a table. Include a search input above the table.` | ||
| - `Display GitHub pull requests in a table.` | ||
| 1. After Bits AI responds to your prompt, you can click **Edit with AI** or manually [customize your app][15]. | ||
| 1. By default, App Builder saves automatically. You can disable auto-save by clicking the gear <i class="icon-cog-2"></i> icon. To save the app manually, click **Save**. |
There was a problem hiding this comment.
Why is it relevant here? Also, I think the auto-save kicks in only after the first time the user saves the app
There was a problem hiding this comment.
I was trying to be thorough about info on saving because I realized I hadn't mentioned the new auto-save feature anywhere, but I think it might be cluttering the instructions now. 🤨 Do you think I should move that info somewhere else, or just cut it back to, To save the app, click Save. ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Messed up the branch name on #29829
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes