Google Dialogflow StrawberryEverything Google Dialogflow knows about your contexts, worked
It reads every context your Google Dialogflow account holds, drafts the changes that follow, and hands you a card for each one before a single context moves.
Open the context. Check it against something else. Write the change. Move to the next one. That is the Google Dialogflow afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a context until you approve it.
What it can do is exactly what Google Dialogflow exposes to an account you authorise and nothing beyond it: 20 operations, 8 reads and 12 writes. In practice that means it can update an entity type, update a context and delete an intent, and work across the contexts, entity types and intents.
The Google Dialogflow API stops at Google Dialogflow. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Can it list intents on its own?
8 of the 20 operations are reads.
Your account, not a guess at it: a companion can list intents, get an entity type and list entity types, and the full list below is the whole list, with nothing inferred from Google Dialogflow's documentation.
The contexts are what most of this inventory is about, alongside the entity types. A companion can hold all 20 of these operations and forty open tabs in the same pass, which is how an afternoon of Google Dialogflow admin becomes a queue you review.
- List Intents
- Get Entity Type
- List Entity Types
- List Contexts
- Get Intent
- Get Context
- Get Agent
- Detect Intent
Which contexts wait for your approval?
All 12 write operations wait for you.
A companion can update an entity type, update a context and delete an intent, and each one is staged on an approval card first: you see the context, the field and the new value before it lands in Google Dialogflow.
Nothing in Google Dialogflow is sent, changed or deleted on your behalf without that click, and a rejected card leaves the context exactly as it was. The gate is the same one on every surface, described at security.
- Update Entity Type
- Update Context
- Delete Intent
- Delete Entity Type
- Delete Entities
- Delete Context
- Delete Agent
- Create or Update Agent
- Create Intent
- Create Entity Type
- Create Entities
- Create Context
Can it update entity type on a schedule?
Yes.
Saved as a routine, the Google Dialogflow contexts pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Google Dialogflow contexts sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents