Starting point
Product data & editorial
Prepare product copy from approved item data
Approved item data and source documents provide the basis for product copy with traceable claims. An editor reviews every draft; missing attributes or conflicting evidence stay open for clarification instead of becoming invented benefits in a shop description.
Process architecture
From an approved item to an editor-reviewed draft.
The item list supplies identifiers and attributes while the document library supplies supporting sources. A model drafts copy that is checked against the data and then reviewed by an editor. Only a reviewed draft becomes a handover document; this workflow does not publish anything to a shop.
01Input
Item & sources
An item released for copy preparation is detected and enriched with approved data sheets and the appropriate writing template.
2 Steps
02Process
Draft & review
Claims are drafted from the evidence, checked for gaps and presented to an editor for a business decision.
5 Steps
03Output
Handover & version record
Reviewed copy is available in an editable document; the item status and source version remain traceable.
4 Steps
Source01Capture the item
Google Sheets API reads released item records in a scheduled check. Item identifier and data version form the case key so that the same state is not processed repeatedly.Details
Capture the item
Google Sheets API reads released item records in a scheduled check. Item identifier and data version form the case key so that the same state is not processed repeatedly.
Interfaces
- Microsoft Graph API
- SharePoint API
Next steps
- Match the sources
Data02Match the sources
Google Drive API retrieves approved data sheets and the writing template for the item. The source selection is recorded, and missing or unreadable documents are explicitly flagged.Details
Match the sources
Google Drive API retrieves approved data sheets and the writing template for the item. The source selection is recorded, and missing or unreadable documents are explicitly flagged.
Interfaces
- Azure AI Document Intelligence
- Mistral OCR
- Dataverse API
Next steps
- Draft product copy
Action03Draft product copy
Vertex AI drafts a title, short copy and description only from supplied attributes. Claims retain source references; unknown values are returned as gaps instead of being invented.Details
Draft product copy
Vertex AI drafts a title, short copy and description only from supplied attributes. Claims retain source references; unknown values are returned as gaps instead of being invented.
Interfaces
- Power Automate
- Azure Functions
- Microsoft Graph API
Next steps
- Check the evidence
Decision04Check the evidence
A comparison checks required fields, numbers, units and source references. It cannot guarantee that prose is correct, so every complete draft also goes through editorial review.Details
Check the evidence
A comparison checks required fields, numbers, units and source references. It cannot guarantee that prose is correct, so every complete draft also goes through editorial review.
Interfaces
- Azure OpenAI GPT
- Anthropic Claude
- AI Builder
Next steps
- Review the wordingEvidence complete
- Clarify missing detailsMissing details
Approval05Review the wording
Google Chat API presents the copy and sources to the responsible editor. They check implied claims too and send revised drafts back through review before authorizing handover.Details
Review the wording
Google Chat API presents the copy and sources to the responsible editor. They check implied claims too and send revised drafts back through review before authorizing handover.
Interfaces
- Teams Adaptive Cards
- Power Apps
Next steps
- Create the documentEditorially reviewed
- Draft product copyRevise
Approval06Clarify missing details
Missing attributes or conflicting sources reach the product owners through Google Chat API. Only completed and approved source data returns to a new drafting pass.Details
Clarify missing details
Missing attributes or conflicting sources reach the product owners through Google Chat API. Only completed and approved source data returns to a new drafting pass.
Interfaces
- Teams Adaptive Cards
- Power Apps
Next steps
- Match the sourcesSource updated
- Defer the caseStill unresolved
System07Create the document
Google Docs API writes the approved draft into the editorial template. The document is linked to its source version; a handover is not marked complete without confirmed storage.Details
Create the document
Google Docs API writes the approved draft into the editorial template. The document is linked to its source version; a handover is not marked complete without confirmed storage.
Interfaces
- Dynamics 365 API
- Azure Service Bus
Next steps
- Provide the draft
Result08Provide the draft
The editor receives an editable Google Docs document containing title, short copy, description and source notes. Importing it into a shop and publishing it are separate decisions.Details
Provide the draft
The editor receives an editable Google Docs document containing title, short copy, description and source notes. Importing it into a shop and publishing it are separate decisions.
Interfaces
- Power BI API
- Teams Webhook
Next steps
- Update item status
- File review evidence
Result09Update item status
Google Sheets API sets an editorially reviewed status and records the document link. This status applies to the checked data version and does not claim that publication occurred.Details
Update item status
Google Sheets API sets an editorially reviewed status and records the document link. This status applies to the checked data version and does not claim that publication occurred.
Interfaces
- Power BI API
- Teams Webhook
Result10File review evidence
Google Drive API files the item state, source references and editorial decision in a restricted item folder. Deferred cases retain a record of their unresolved questions as well.Details
File review evidence
Google Drive API files the item state, source references and editorial decision in a restricted item folder. Deferred cases retain a record of their unresolved questions as well.
Interfaces
- Power BI API
- Teams Webhook
Result11Defer the case
If a required attribute cannot be supported, the item remains deferred with an owner and an open question. It receives neither a reviewed-copy status nor a supposedly complete document.Details
Defer the case
If a required attribute cannot be supported, the item remains deferred with an owner and an open question. It receives neither a reviewed-copy status nor a supposedly complete document.
Interfaces
- Power BI API
- Teams Webhook
Next steps
- File review evidence
System landscape
Google Workspace connects data and editorial work.
- Microsoft
Microsoft Graph API
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
SharePoint API
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Azure AI Document Intelligence
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Mistral OCR
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Dataverse API
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Power Automate
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Azure Functions
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Azure OpenAI GPT
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Anthropic Claude
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
AI Builder
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Teams Adaptive Cards
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Power Apps
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Dynamics 365 API
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Azure Service Bus
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Power BI API
Möglicher Baustein für die Microsoft-Systemvariante.
- Microsoft
Teams Webhook
Möglicher Baustein für die Microsoft-Systemvariante.
- Interfaces in use
Google Sheets API
Reads approved item states and records the reviewed status with a document link.
- Interfaces in use
Google Drive API
Retrieves approved source documents and files the source state and decision evidence for the item.
- Interfaces in use
Vertex AI
Drafts copy from supplied attributes with source references without inventing missing product details.
- Interfaces in use
Google Chat API
Presents copy and unresolved attributes to the responsible editorial and product roles.
- Interfaces in use
Google Docs API
Creates the editable handover document from the agreed template after business review.
- Possible apps & platforms
Google Sheets
Product owners maintain approved item states and see processing status and document links.
- Possible apps & platforms
Google Drive
Authorized staff maintain data sheets and retrieve evidence supporting editorial decisions.
- Possible apps & platforms
Google Chat
Editors review drafts and product owners resolve missing or contradictory information.
- Possible apps & platforms
Google Docs
Reviewed copy is supplied as an editable draft for later channel handover.
Implementation in context
Keep product descriptions tied to their evidence.
This process prepares product-copy drafts from approved data rather than answering general knowledge questions. The Google Sheets list is an editorial working source, not a replacement for an ERP or product-data system. A handover document is neither imported into the shop nor publicly published by this workflow.
Required attributes and permitted claims are agreed for each product group. Numbers, units, materials and usage limits must come from the item record or approved evidence; certifications, compatibility and performance are not inferred from similar items. A rules-based check identifies certain gaps, while the editor remains responsible for every wording decision.
Source access is restricted to authorized product and editorial roles. Only approved content needed for the item is passed to the configured model; processing region, retention and data handling must be agreed in advance. Supplier prose is input data and cannot introduce system instructions or authorize publication.
Item identifier, data version and template identify the draft that was reviewed. If the evidence changes before handover, the comparison runs again instead of silently overwriting reviewed copy. Integration failures remain visible, and retries check for existing documents before creating another handover version.
Target picture
Every product text starts with an approved item state and traceable sources. A draft receives business review before becoming an editable handover document; unresolved attributes prevent a misleadingly complete description.
Expected benefits
- Editors receive a structured draft with its supporting evidence rather than scattered inputs.
- Missing attributes remain visible rather than being replaced with plausible product promises.
- Each handed-over text has a reviewed data and template version.
- Item status distinguishes drafting, editorial review and later publication.
- Source references and decisions remain findable when a product attribute changes.
Prerequisites to start
- 01A maintained item list contains unique identifiers, versions, required fields and an editorial-processing status.
- 02Approved data sheets are clearly linked and available in a readable processing format.
- 03Each product group has a writing template, permitted claims and a named business owner.
- 04Google Workspace access and a Google Cloud project are configured with the required limited permissions.
- 05Model region, data handling, source access and retention are agreed with the business.
- 06An editor reviews every draft while shop import and public publication remain outside this process.
More use cases
Matching solutions from your industry
Sales & quotes
Follow up on open quotes automatically
Every quote that stays unanswered is followed up automatically, at the agreed interval and in the same conversation as the quote itself. The process builds on the environment already in place – Microsoft 365, Google Workspace or a self-hosted ERP – and sales only decides the exceptions.
Every open quote has a defined follow-up path that works without a person remembering it. Sales can see which quotes are still alive and is only needed where a decision is due. What remains on each quote is a traceable series of attempts instead of an assumption.
- Microsoft Graph API
- Microsoft Dynamics 365 Sales API
- Gmail API
- Google Sheets API
Email & intake channels
Understand and route incoming messages automatically
AI identifies requests, attachments and priorities, then moves every message into the right downstream workflow with clear controls.
Faster response times, consistent ownership and a traceable status from the first customer contact.
- Microsoft Graph / Gmail API
- CRM- oder Ticket-API
- Webhook / REST
- Outlook & Microsoft Teams
Sales & quoting
Turn customer inquiries into finished quotes automatically
Every customer inquiry from the shared mailbox and the web form is extracted, priced against the item master and the agreed terms, and sent as a complete quote. Only unmatched lines or discounts outside the rules reach inside sales; everything else leaves the company the same day.
Every inquiry leads to a complete quote with a number, line items and a validity period on the same day. Inside sales only decides where the match is missing or the price leaves the agreed rules, and each of those decisions stays on the case with its basis.
- Microsoft Graph / Gmail API
- Azure AI Document Intelligence / Google Document AI
- Azure OpenAI Service / Vertex AI / Ollama
- ERP REST / OData / Google Sheets API
Purchasing & inventory
Trigger reorders automatically at minimum stock
Every item that drops below its reorder point is automatically turned into a purchase proposal. Purchasing only reviews exceptional cases and approves, instead of reconciling stock lists and open orders by hand.
Every item drops below its reorder point at most until the next run before a purchase proposal exists. Purchasing only decides where the rules are not clear-cut, and each decision is documented together with its basis.
- Microsoft Dynamics 365 Business Central API
- Azure OpenAI Service
- Microsoft Power Automate
- Microsoft Teams Adaptive Cards
Purchasing & goods receipt
Resolve discrepancies at goods receipt
Received quantities, item lines and visible damage are compared with the purchase order and delivery note. When something differs, purchasing gets a reviewable case with photographs and documents; only accepted quantities are posted to the system of record.
Each shipment has one case linking the order, received quantities and supporting evidence. Matching lines can be posted; a purchasing person decides discrepancies against a specific difference before any query reaches the supplier.
- Google Forms API
- ERP REST API
- Google Document AI
- Google Chat API
Finance and receivables
Send payment reminders from overdue invoices automatically
Every overdue open item from Microsoft Dynamics 365 Business Central, DATEV or the line-of-business system is checked against due date, grace period and reminder level and sent as a payment reminder through Microsoft Outlook or Gmail. Only blocked customers, missing recipients and amounts outside the agreed level go to finance; everything else leaves the same day.
Every overdue open item receives the next allowed reminder from the stored template as soon as due date and grace period are met. Only blocked customers, missing recipient addresses and amounts outside the agreed level reach finance as a case ready for a decision. Send, reminder level and record sit in the system of record, not in a private list.
- Microsoft Graph API
- Gmail API
- REST API
- Webhook
Your next step
Which process costs your team unnecessary time every day?
Give us a short outline. We will tell you honestly where automation is useful—and where it is not.
