An AI agent workflow connects a request to a result through the information the agent reads, the tools it uses and the decisions people review. In ChannelGate, you can start that work in Slack and continue the conversation as the agent returns a draft, asks for clarification or proposes an action within its configured access.
This walkthrough follows one request from beginning to end: preparing a project handover. You will see what the person using ChannelGate does and what happens behind each step. The handover brings agreed scope, owners, dates and open questions into a document the next person can use.
Read the video transcript
Ask ChannelGate in Slack to prepare a project handover from the available notes and task records. Request scope, owners, confirmed dates and open questions, with source references and a draft for review.
The agent uses the context, instructions and tools configured for the run. Files can supply everything needed for the draft; connected apps are needed only when the task calls for them. Prompt and relevant context go to the selected model provider.
Review the draft against its sources and check missing or conflicting information. Keep kickoff provisional if no date is confirmed, and leave delivery ownership open until the proposed owner accepts. Ask the agent to carry those corrections into the document, then review the updated version.
If you also want a CRM update, review the intended account, exact record, proposed note and handover link before authorizing the change. This workflow asks for that review explicitly; technical tool approval behavior depends on the engine and configured settings.
After an authorized update, check the saved CRM record and its link. Open the shared handover document and confirm that the next owner can access it.
How do you start an AI agent workflow in Slack?
Ask for the result you need and name the material the agent should use. In this example, the project notes and task records are already available in the channel's working folder.
Your request
@ChannelGate, prepare a project handover from these notes and task records. Include agreed scope, owners, confirmed dates and open questions. Link commitments to their sources and save a draft for review. Ask before updating the CRM or contacting anyone.
What happens behind the request: ChannelGate checks whether you can use the channel. The selected agent receives the conversation context and the instructions, skills and tools available for this run. Those settings determine what it can work with; mentioning a CRM in a message does not grant access to it. The documented capabilities describe these controls.
What information and connected tools does the agent use?
For this handover, the agent needs the agreed scope, kickoff notes and task records. It can read the available files and use their contents to assemble the document. If something essential is missing, the useful next step is a clarification, such as asking where the final scope was saved.
What you see: a question about missing information or a draft based on the available sources. Ask the agent to name the sources it used so you can check them.
What happens behind it: files provide the source material; connected tools allow the agent to retrieve information or perform actions in an external app when access is granted. An inbox connection is unnecessary when the relevant email excerpts are already provided as files. A CRM update later in this workflow needs an available connection and permission to make that change.
ChannelGate separates personal and agent connection identities. A request for your own inbox uses your personal connection, and an external update needs the intended account. See how connections and account access work. Prompt and relevant context go to the selected model provider; connected apps also use their own external services.
What does the first answer look like?
What you receive: a saved handover draft you can open, with source references and unresolved questions. The answer in Slack should link to the document and identify decisions that still need your input.
What happens behind the answer: the agent assembles the source material into the requested structure. That draft still needs checking against the agreement. Start with scope, dates and responsibilities, because those are the details that guide delivery. Compare the draft with the agreed scope before treating a task or email discussion as a new commitment.
For an intake-process handover, the handover should separate the work agreed for this phase from the reporting dashboard discussed for later. If the notes propose a delivery owner without recording acceptance, keep the assignment open. If kickoff depends on a decision still outstanding, keep the date provisional.
A useful draft passage would read:
Kickoff remains provisional. The delivery owner still needs to accept the assignment. A reporting dashboard is under discussion for a later phase and is excluded from the current agreed scope.
The source references alongside those statements let the reviewer check each one. Where two sources disagree, preserve the disagreement and ask the project owner to resolve it.
How do you correct the draft?
What you do: reply in the same thread with the correction or missing decision. Human review adds decisions as well as corrections. The reviewer can clarify how an unresolved item should be handled, then ask the agent to carry that instruction through the document.
Example review instruction
Keep kickoff provisional and assign the date-confirmation follow-up to the project owner. Keep the reporting dashboard in the excluded-scope section. Confirm the delivery owner's acceptance before marking the assignment as settled.
What happens next: the agent revises the document using your clarification. Check that the revision affects every relevant section, including the summary, open questions and next actions. A correction acknowledged only in chat leaves the handover incomplete.
Draft wording
Kickoff is provisional. A delivery owner is proposed. Reporting is possible later work outside the agreed scope.
After the review instruction
No kickoff date is confirmed. The project owner is responsible for the date-confirmation follow-up. Delivery ownership awaits acceptance. The reporting dashboard stays outside this phase's scope.
Record the new instruction in a reviewer change log. Distinguish it from facts in the original source files: the reviewer has added a follow-up responsibility, so the reference for that decision is the review exchange.
When does the workflow need your approval?
What you review: the proposed action before it changes another system. In this example, ask the agent to prepare a CRM update for your approval after the handover is accepted. This is an optional next step.
Accepting the document establishes which version is ready to use. Save the reviewed version in the team’s intended document location and check that the next owner can open it. Use that version’s shareable URL for any reference you add elsewhere.
If the next step is to add its reference to a CRM record, review that action separately. The proposal needs the intended account, the exact destination record, the note to add and the working document URL.
What to review before the update
Account: the intended connected CRM account, with its service owner verified.
Target: the exact project or deal record, including its identifier.
Change: the proposed note and the accepted handover's URL.
A note could summarize the agreed scope, state that kickoff and delivery ownership still need confirmation, and link to the reviewed document for the details.
Example approval, after those details are filled in
I approve adding the reviewed note and handover URL to the specified record using the account shown above.
Review the concrete action before authorizing it. If the account, destination or note changes, review the revised proposal. What happens behind it: ChannelGate's governance settings, selected engine and approval settings determine whether a tool action can proceed, needs review or is refused. Not every action displays a human approval prompt. An instruction to ask before a CRM update and a technical approval control are different; the engine capability matrix describes the available behavior.
After the authorized update, reopen the same record and check the saved note and link. Open the document as well and confirm that the next owner can access it.
What do you receive at the end?
Your result: a reviewed handover document, a clear list of remaining decisions and, if you authorized a CRM update, a checked reference on the intended record.
The final document should keep confirmed commitments and unresolved decisions easy to tell apart. For this process, the completed handover would contain the following sections, filled from the actual sources and review decisions:
Handover document structure
Ready for the next owner
Agreed scope: the work included in this phase, with references to the agreement.
Exclusions: later ideas and requests that have not been accepted into scope.
Owners and dates: confirmed responsibilities and timing, with provisional items clearly marked.
Open questions: missing decisions, who needs to resolve them and where the answer will be recorded.
Next actions: concrete follow-ups based on the remaining work and review instructions.
Change log: the corrections made during review and the decision behind each one.
Document reference: the accepted version and, if it was added to the CRM, the destination record checked after the update.
The workflow is finished when the team has checked the document, resolved or assigned the open questions, and verified any authorized update. The project owner still decides what is agreed and who is accountable; the agent helps turn those decisions and their sources into a usable record.
The same pattern can support other operations workflows in Slack: define the output, provide the context, review the work and verify any action taken in another system.
What needs to be ready before your team starts?
Start with a small set of relevant material in the channel's working folder. Give each source a clear name so a reviewer can follow a claim back to the agreement, meeting note or task that supports it.
| Source | What it contributes | What to check |
|---|---|---|
| Agreed scope | Deliverables and exclusions | Which work has actually been agreed |
| Kickoff notes | Proposed sequence, dates and responsibilities | Which suggestions still need confirmation |
| Email excerpts | Clarifications and changes discussed with stakeholders | Whether a proposal became a commitment |
| Task records | Assignments, status and next actions | Whether the tasks match the agreement |
Choose who will review the draft, give the agent access to the relevant files and enable the tools needed to create the document. If the work needs a connected app, select the intended account and confirm its access. ChannelGate's credentials model separates requester and shared connections, so the workflow should make clear whose account will be used.
Configure the review controls before starting. The available tool-approval behavior depends on the engine and settings, as documented in the engine capability matrix. An instruction to ask before a CRM update and a configured technical approval control serve different purposes; check both for the workflow you intend to run.
ChannelGate supports file work and connected business tools within the configured access. Relevant source content can reach the selected model provider, so select material that is appropriate for that processing.
Frequently asked questions
Does every AI agent workflow need connected apps?
No. This example can produce a reviewed handover from files in the working folder. Connected apps become necessary when the work requires information or actions in those services. If you want the agent to gather material from an inbox or another app, enable the required connection and identify the account and search scope first.
What happens when sources disagree?
Keep the disagreement visible and ask the project owner to resolve it. Preserve both references and record the decision. A newer task or email does not automatically replace the agreed scope.
Does accepting the document approve the CRM update?
No. Review the exact note, document URL, account and target record separately. Accepting the handover establishes which document is ready to use; authorizing the CRM action determines where its reference can be added.
Can I use this as a first implementation brief?
Yes. Choose one project, a reviewer, a small source pack and an output they can check. Define the review steps and destination check before the run. The implementation page explains how Makeitfuture helps scope that first workflow.