Things to try

Good prompts name the site, the task, and the time period. The examples below are starting points; the assistant’s results depend on your data, permissions, and the tools available.

Get oriented

Try this prompt

List the sites I can access. For example.com, show the widgets and their current status. Do not make changes.

Use this to check that the connection is working with the right account before doing anything else.

Review popup performance

Try this prompt

For example.com, compare widget performance for October 1–7 and October 8–14, 2026. Explain the date boundaries and metrics you use. Flag missing data instead of treating it as zero.

Replace the example dates with your reporting periods. Ask for the raw figures alongside the explanation.

Understand an automation

Try this prompt

Find the welcome automation on example.com. Explain its trigger, steps, and current status. Identify anything you cannot determine from the available data. Do not change it.

This is useful when you are checking an existing setup or preparing to make a change.

Prepare a widget edit

Try this prompt

On example.com, find the newsletter signup popup. Read its current content and targeting, then suggest clearer headline and button text. Show the proposed changes before applying anything.

Once you have reviewed the proposal, you can ask for a specific supported edit. Confirm which widget or editor draft the assistant is working on.

Make requests easier to verify

• Name the site in every new conversation.
• Use explicit dates for reporting.
• Ask for current state before requesting a change.
• Review the returned result and check the object in your dashboard.

A request to “ask before changing” is an instruction to your assistant. It does not reduce the permissions granted to the connection.