Each setting has a different job
| Setting | Controls | Does not do |
|---|---|---|
| Agent role and instructions | Purpose, expertise, preferred outputs and context | Grant access to a company or connected account. |
| Suggestions during work | Proactive, Guided or On request behavior | Replace the map’s start condition. |
| What to flag | Critical, Risks or Full review attention | Change which users may see private records. |
| Level of detail | How much explanation accompanies the answer | Increase access or authorize an external write. |
| Action map | Executable steps, input sources, decisions and approvals | Guarantee that future tasks contain usable data. |
| Start condition | Manual, scheduled or supported event/condition-based execution | Automatically run merely because the chat is open. |
Choose the launch rhythm
- 1Open the start block
Choose the launch mode in the action map rather than writing a schedule only in free-text instructions.
- 2Configure timing
For a schedule, select the available frequency, time and time zone. For a trigger, identify the event or condition and the project data it observes.
- 3Save and check the next run
Confirm the map is saved and the relationship is active. Check that the displayed next run agrees with your intended local time.
- 4Request an extra check when necessary
A manual run is separate from the regular schedule. Review active executions before starting another external write.
Configure authority where it is used
Company and project access determine what the agent may reach. Connected accounts determine the MCP tools and resources available. Individual actions define what to read or change and any approval needed.
CRM details belong to the CRM action; a recipient source belongs to the email action. General behavior settings do not substitute for those inputs.
Make the behavior fit the work
| Need | Useful starting configuration |
|---|---|
| Daily delivery overview | A daily start condition; Guided suggestions; Risks attention; concise output. |
| Research on demand | A manual start; relevant sources; detailed evidence and a saved report. |
| Client-data intake | A task source and tag condition; a data-present branch; a CRM action; a no-data finish. |
Change the route through chat or the canvas
Describe the change precisely, for example: “Replace the spreadsheet output with saving the client to CRM when contact details are present; otherwise finish.” Inspect the proposed change and use its apply control when offered.
Confirm the saved map actually contains the new step and routes. A planning message, review note or Retry changes card does not mean the map changed. If validation fails, open the stated issue and correct the selected step.
Verify the result
- The saved start condition matches the expected cadence.
- The new step has its source fields and connected account.
- Every decision has a route for an unmatched or empty result.
- The run history and resulting record confirm what happened.