mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-05 06:59:23 +00:00
a237ebabba
* 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>
62 lines
2.8 KiB
Plaintext
62 lines
2.8 KiB
Plaintext
---
|
|
title: "HubSpot 트리거"
|
|
description: "HubSpot 워크플로우에서 CrewAI 크루를 직접 트리거하세요"
|
|
icon: "hubspot"
|
|
mode: "wide"
|
|
---
|
|
|
|
이 가이드는 HubSpot Workflows에서 직접 crew를 시작할 수 있도록 CrewAI AOP용 HubSpot 트리거를 설정하는 단계별 과정을 제공합니다.
|
|
|
|
## 사전 준비 사항
|
|
|
|
- CrewAI AMP 계정
|
|
- [HubSpot Workflows](https://knowledge.hubspot.com/workflows/create-workflows) 기능이 활성화된 HubSpot 계정
|
|
|
|
## 설정 단계
|
|
|
|
<Steps>
|
|
<Step title="HubSpot 계정을 CrewAI AOP와 연결하기">
|
|
- `CrewAI AMP 계정 > 트리거`에 로그인합니다. - 사용 가능한 트리거 목록에서
|
|
`HubSpot`을 선택합니다. - CrewAI AOP와 연결하고자 하는 HubSpot 계정을
|
|
선택합니다. - 화면에 나타나는 안내에 따라 CrewAI AOP가 HubSpot 계정에
|
|
접근하도록 승인합니다. - HubSpot이 CrewAI AOP와 성공적으로 연결되면 확인
|
|
메시지가 표시됩니다.
|
|
</Step>
|
|
<Step title="HubSpot 워크플로우 생성하기">
|
|
- `HubSpot 계정 > 자동화 > 워크플로우 > 새 워크플로우`에 로그인합니다. -
|
|
필요에 맞는 워크플로우 유형을 선택합니다 (예: 처음부터 시작). - 워크플로우
|
|
빌더에서 더하기(+) 아이콘을 클릭하여 새로운 작업을 추가합니다. - `통합 앱 >
|
|
CrewAI > Crew 시작하기`를 선택합니다. - 시작할 Crew를 선택합니다. - `저장`을
|
|
클릭하여 워크플로우에 작업을 추가합니다.
|
|
<Frame>
|
|
<img
|
|
src="/images/enterprise/hubspot-workflow-1.png"
|
|
alt="HubSpot Workflow 1"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
<Step title="Crew 결과를 다른 작업과 함께 사용하기">
|
|
- Crew 시작 단계 이후, 더하기(+) 아이콘을 클릭하여 새로운 작업을 추가합니다.
|
|
- 예를 들어, 내부 이메일 알림을 전송하려면 `커뮤니케이션 > 내부 이메일 알림
|
|
전송`을 선택합니다. - 본문 필드에서 `데이터 삽입`을 클릭하고, `다음에서 속성
|
|
또는 작업 결과 보기 > 작업 결과 > Crew 결과`를 선택하여 이메일에 Crew
|
|
데이터를 포함합니다.
|
|
<Frame>
|
|
<img
|
|
src="/images/enterprise/hubspot-workflow-2.png"
|
|
alt="HubSpot Workflow 2"
|
|
/>
|
|
</Frame>
|
|
- 필요에 따라 추가 작업을 구성합니다. - 모든 워크플로우 단계를
|
|
검토하여 올바르게 설정되었는지 확인합니다. - 워크플로우를 활성화합니다.
|
|
<Frame>
|
|
<img
|
|
src="/images/enterprise/hubspot-workflow-3.png"
|
|
alt="HubSpot Workflow 3"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
</Steps>
|
|
|
|
사용 가능한 작업과 사용자 지정 옵션에 대한 자세한 정보는 [HubSpot 워크플로우 문서](https://knowledge.hubspot.com/workflows/create-workflows)를 참고하세요.
|