mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-03 06:08:15 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
241 lines
7.6 KiB
Plaintext
241 lines
7.6 KiB
Plaintext
---
|
|
title: Microsoft Word Integration
|
|
description: "Document creation and management with Microsoft Word integration for CrewAI."
|
|
icon: "file-word"
|
|
mode: "wide"
|
|
---
|
|
|
|
## Overview
|
|
|
|
Enable your agents to create, read, and manage Word documents and text files in OneDrive or SharePoint. Automate document creation, retrieve content, manage document properties, and streamline your document workflows with AI-powered automation.
|
|
|
|
## Prerequisites
|
|
|
|
Before using the Microsoft Word integration, ensure you have:
|
|
|
|
- A [CrewAI AMP](https://app.crewai.com) account with an active subscription
|
|
- A Microsoft account with Word and OneDrive/SharePoint access
|
|
- Connected your Microsoft account through the [Integrations page](https://app.crewai.com/crewai_plus/connectors)
|
|
|
|
## Setting Up Microsoft Word Integration
|
|
|
|
### 1. Connect Your Microsoft Account
|
|
|
|
1. Navigate to [CrewAI AMP Integrations](https://app.crewai.com/crewai_plus/connectors)
|
|
2. Find **Microsoft Word** in the Authentication Integrations section
|
|
3. Click **Connect** and complete the OAuth flow
|
|
4. Grant the necessary permissions for file access
|
|
5. Copy your Enterprise Token from [Integration Settings](https://app.crewai.com/crewai_plus/settings/integrations)
|
|
|
|
### 2. Install Required Package
|
|
|
|
```bash
|
|
uv add crewai-tools
|
|
```
|
|
|
|
### 3. Environment Variable Setup
|
|
|
|
<Note>
|
|
To use integrations with `Agent(apps=[])`, you must set the
|
|
`CREWAI_PLATFORM_INTEGRATION_TOKEN` environment variable with your Enterprise
|
|
Token.
|
|
</Note>
|
|
|
|
```bash
|
|
export CREWAI_PLATFORM_INTEGRATION_TOKEN="your_enterprise_token"
|
|
```
|
|
|
|
Or add it to your `.env` file:
|
|
|
|
```
|
|
CREWAI_PLATFORM_INTEGRATION_TOKEN=your_enterprise_token
|
|
```
|
|
|
|
## Available Actions
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="microsoft_word/get_documents">
|
|
**Description:** Get all Word documents from OneDrive or SharePoint.
|
|
|
|
**Parameters:**
|
|
- `select` (string, optional): Select specific properties to return.
|
|
- `filter` (string, optional): Filter results using OData syntax.
|
|
- `expand` (string, optional): Expand related resources inline.
|
|
- `top` (integer, optional): Number of items to return (min 1, max 999).
|
|
- `orderby` (string, optional): Order results by specified properties.
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/create_text_document">
|
|
**Description:** Create a text document (.txt) with content. RECOMMENDED for programmatic content creation that needs to be readable and editable.
|
|
|
|
**Parameters:**
|
|
- `file_name` (string, required): Name of the text document (should end with .txt).
|
|
- `content` (string, optional): Text content for the document. Default is "This is a new text document created via API."
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/get_document_content">
|
|
**Description:** Get the content of a document (works best with text files).
|
|
|
|
**Parameters:**
|
|
- `file_id` (string, required): The ID of the document.
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/get_document_properties">
|
|
**Description:** Get properties and metadata of a document.
|
|
|
|
**Parameters:**
|
|
- `file_id` (string, required): The ID of the document.
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/delete_document">
|
|
**Description:** Delete a document.
|
|
|
|
**Parameters:**
|
|
- `file_id` (string, required): The ID of the document to delete.
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/copy_document">
|
|
**Description:** Copy a document to a new location in OneDrive.
|
|
|
|
**Parameters:**
|
|
- `file_id` (string, required): The ID of the document to copy
|
|
- `name` (string, optional): New name for the copied document
|
|
- `parent_id` (string, optional): The ID of the destination folder (defaults to root)
|
|
|
|
</Accordion>
|
|
|
|
<Accordion title="microsoft_word/move_document">
|
|
**Description:** Move a document to a new location in OneDrive.
|
|
|
|
**Parameters:**
|
|
- `file_id` (string, required): The ID of the document to move
|
|
- `parent_id` (string, required): The ID of the destination folder
|
|
- `name` (string, optional): New name for the moved document
|
|
|
|
</Accordion>
|
|
</AccordionGroup>
|
|
|
|
## Usage Examples
|
|
|
|
### Basic Microsoft Word Agent Setup
|
|
|
|
```python
|
|
from crewai import Agent, Task, Crew
|
|
|
|
# Create an agent with Microsoft Word capabilities
|
|
word_agent = Agent(
|
|
role="Document Manager",
|
|
goal="Manage Word documents and text files efficiently",
|
|
backstory="An AI assistant specialized in Microsoft Word document operations and content management.",
|
|
apps=['microsoft_word'] # All Word actions will be available
|
|
)
|
|
|
|
# Task to create a new text document
|
|
create_doc_task = Task(
|
|
description="Create a new text document named 'meeting_notes.txt' with content 'Meeting Notes from January 2024: Key discussion points and action items.'",
|
|
agent=word_agent,
|
|
expected_output="New text document 'meeting_notes.txt' created successfully."
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(
|
|
agents=[word_agent],
|
|
tasks=[create_doc_task]
|
|
)
|
|
|
|
crew.kickoff()
|
|
```
|
|
|
|
### Reading and Managing Documents
|
|
|
|
```python
|
|
from crewai import Agent, Task, Crew
|
|
|
|
# Create an agent focused on document operations
|
|
document_reader = Agent(
|
|
role="Document Reader",
|
|
goal="Retrieve and analyze document content and properties",
|
|
backstory="An AI assistant skilled in reading and analyzing document content.",
|
|
apps=['microsoft_word/get_documents', 'microsoft_word/get_document_content', 'microsoft_word/get_document_properties']
|
|
)
|
|
|
|
# Task to list and read documents
|
|
read_docs_task = Task(
|
|
description="List all Word documents in my OneDrive, then get the content and properties of the first document found.",
|
|
agent=document_reader,
|
|
expected_output="List of documents with content and properties of the first document."
|
|
)
|
|
|
|
crew = Crew(
|
|
agents=[document_reader],
|
|
tasks=[read_docs_task]
|
|
)
|
|
|
|
crew.kickoff()
|
|
```
|
|
|
|
### Document Cleanup and Organization
|
|
|
|
```python
|
|
from crewai import Agent, Task, Crew
|
|
|
|
# Create an agent for document management
|
|
document_organizer = Agent(
|
|
role="Document Organizer",
|
|
goal="Organize and clean up document collections",
|
|
backstory="An AI assistant that helps maintain organized document libraries.",
|
|
apps=['microsoft_word/get_documents', 'microsoft_word/get_document_properties', 'microsoft_word/delete_document']
|
|
)
|
|
|
|
# Task to organize documents
|
|
organize_task = Task(
|
|
description="List all documents, check their properties, and identify any documents that might be duplicates or outdated for potential cleanup.",
|
|
agent=document_organizer,
|
|
expected_output="Analysis of document library with recommendations for organization."
|
|
)
|
|
|
|
crew = Crew(
|
|
agents=[document_organizer],
|
|
tasks=[organize_task]
|
|
)
|
|
|
|
crew.kickoff()
|
|
```
|
|
|
|
## Troubleshooting
|
|
|
|
### Common Issues
|
|
|
|
**Authentication Errors**
|
|
|
|
- Ensure your Microsoft account has the necessary permissions for file access (e.g., `Files.Read.All`, `Files.ReadWrite.All`).
|
|
- Verify that the OAuth connection includes all required scopes.
|
|
|
|
**File Creation Issues**
|
|
|
|
- When creating text documents, ensure the `file_name` ends with `.txt` extension.
|
|
- Verify that you have write permissions to the target location (OneDrive/SharePoint).
|
|
|
|
**Document Access Issues**
|
|
|
|
- Double-check document IDs for correctness when accessing specific documents.
|
|
- Ensure the referenced documents exist and are accessible.
|
|
- Note that this integration works best with text files (.txt) for content operations.
|
|
|
|
**Content Retrieval Limitations**
|
|
|
|
- The `get_document_content` action works best with text files (.txt).
|
|
- For complex Word documents (.docx), consider using the document properties action to get metadata.
|
|
|
|
### Getting Help
|
|
|
|
<Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
|
|
Contact our support team for assistance with Microsoft Word integration setup
|
|
or troubleshooting.
|
|
</Card>
|