AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
TypeScript ai-agentai-agent-toolsai-agentsai-agents-frameworkmcpmcp-servermcp-toolsmcpsn8n-alternativeno-code-automationworkflowworkflow-automationworkflows
docs: refresh Get Started and Enterprise Control content and media (#15399)
mintlify[bot]85fb745b7b7e
diff --git a/brain/knowledge/engineering/ci-pr-review-hygiene.md b/brain/knowledge/engineering/ci-pr-review-hygiene.mdindex a063440f67d..ba558cbf257 100644--- a/brain/knowledge/engineering/ci-pr-review-hygiene.md+++ b/brain/knowledge/engineering/ci-pr-review-hygiene.md@@ -64,3 +64,5 @@ Enforcement is the **`Codeowners review` repository ruleset** (active on the def- **Nothing rolls `## Unreleased` over at release time, and the docs site is unversioned — so a breaking-changes entry has to name its own version.** No workflow or script writes to `docs/install/reference/breaking-changes.mdx` (`breaking-change-check.ts` only reads it), and `git log -S"## 0.88"` on the file comes back empty: the heading has not moved since 0.87.0, so entries for work that shipped months ago still sit under "Unreleased" (PM2 removal in 0.88.2, cache pre-warm gate and workspace naming in 0.89.0, …). `docs/docs.json` has no versioning either, so there is one live page for every self-hoster whatever version they run, published on merge rather than on release — the version heading is the *only* thing telling a reader whether a change is already in their build. So before adding an entry, run `git tag --contains <commit>` on the change it describes and file it under the release that actually shipped it; only genuinely unshipped work belongs under "Unreleased". What points self-hosters at the page in the first place is `release-drafter.yml`, which appends a "review the Breaking Changes page" line to every release body and groups `⛓️💥 breaking-change` PRs under their own heading — which also means a docs-only PR back-documenting an old change shows up in the *next* release's breaking-change list.- **Greptile enforces the file-order rule on *private* constants too, which CLAUDE.md only states for exported ones.** CLAUDE.md says "Exported types and constants must be placed at the end of the file" and gives the order as imports → exports → helpers → types; Greptile reads that as covering module-private constants as well, and flags a `const` sitting above the file's exported symbol (P2 on [#15226](https://github.com/activepieces/activepieces/pull/15226), for two constants only read inside the service they sat above). It has that as a stored custom-context memory, so it will keep raising it. Put private constants in the helpers section below the export — hoisting is a non-issue when they are only read at call time.- **`turbo run lint --filter=<pkg>` never typechecks that package, so "0 errors" is no proof it compiles — run `turbo run build --filter=<pkg>` as well.** A package's `lint` script is `eslint 'src/**/*.ts'` with no `tsc`, and the turbo `lint` task's `dependsOn: ["^build"]` builds the package's *upstream dependencies* only, never itself — the `^` is the whole story. So a type error in the package you are editing is invisible to a filtered lint run. CI still catches it, but confusingly under the **lint** job as well as **main**, because linting the whole repo makes your package an upstream of something else whose `^build` finally compiles it. A branch can therefore sit red on two jobs for one `tsc` error that a local filtered lint reported clean.+- **Docs videos belong on `cdn.activepieces.com/videos/docs/`, never in the repo — and `docs/resources/` is the legacy path that suggests otherwise.** Every `<video>` already in the wiki points at that CDN prefix, but `docs/resources/` still holds ~43 MB of in-repo gifs from before the convention, so the tree itself gives mixed signals and a contributor reasonably copies the wrong one. [#15399](https://github.com/activepieces/activepieces/pull/15399) added a fresh `docs/videos/` folder with 155 MB of `.mp4` against an 880 MB `.git`, including one byte-identical duplicate. Nothing in CI catches it: `PR size` exempts unmatched areas and counts lines, not bytes, and a binary blob contributes zero lines. Review the *file list* of a docs PR, not just its diff. Once such a branch is pushed the blobs are already on the remote — dropping them at the tip only keeps them out of `main` if the PR is **squash**-merged and the branch deleted, so a merge commit ships them permanently. Because the blobs stay reachable until the branch is deleted, nobody has to re-request the assets from whoever recorded them — pull them straight back out of history with `git archive <commit> docs/videos | tar -x --strip-components=2 -C <dir>`, picking the commit *before* the removal, which is also how you get them under the post-rename filenames the pages already reference.+- **Mintlify-editor PRs arrive with `untitled-page*.mdx` at the docs root and `(1)`/`(2)`-suffixed media, wired into `docs.json` under those names.** The bot commits whatever the web editor autosaved, so pages land as `docs/untitled-page-5.mdx` rather than in the folder their nav group implies, and re-uploaded assets keep the browser's download-collision suffix (`data-flow-(1).mp4`, `01---insert-panel-(1.2x).mp4`). Mintlify's own link check passes — the names are internally consistent — so nothing flags it. Rename the files, fix the `docs.json` entries, then diff the *flattened nav tree* against `main` rather than reading the raw JSON diff: the editor also reindents, which buried a real change (the Enterprise Control `Security` group demoted to a child of `Guides`) inside 242 lines of whitespace churn on that PR.diff --git a/docs/admin-guide/guides/embedding.mdx b/docs/admin-guide/guides/embedding.mdxnew file mode 100644index 00000000000..2de130cd91c--- /dev/null+++ b/docs/admin-guide/guides/embedding.mdx@@ -0,0 +1,25 @@+---+title: "Embedding"+icon: "square-a"+---++ Embedding lets you make Activepieces automation capabilities available inside your own product or website.++The Embed Onboarding page helps platform admins configure the platform-level settings required before embedding Activepieces into an application.++### Set up Embedding++The onboarding process has four steps:++1. **Enter the embed URL:** Enter the domain where you want to embed Activepieces. Use a subdomain that your organization controls, for example: flows.acme.com Click Save domain to continue.+2. **Verify the DNS records:** Configure the provided DNS records for your domain and complete the verification process. This connects the domain you entered to your Activepieces embedded environment.+3. **Add allowed domains:** Add the domains that are allowed to host your embedded Activepieces experience. This lets you control which applications or websites can use the embedded experience.+4. **Add signing keys:** Add the signing keys required for your embedded setup. These keys are used as part of the authentication process between your application and Activepieces.++### **Learn more about Embedding**++This page covers the **platform-level setup** for Embedding.++For the complete guide to embedding Activepieces in your application, including user provisioning, authentication, and the **Embed SDK**, see the [Embedding documentation](/embedding/overview).++<br />diff --git a/docs/admin-guide/guides/health.mdx b/docs/admin-guide/guides/health.mdxnew file mode 100644index 00000000000..1447ca41f72--- /dev/null+++ b/docs/admin-guide/guides/health.mdx@@ -0,0 +1,37 @@+---+title: "Health"+icon:+ name: "monitor-heart-rate"+ style: "regular"+ library: "fontawesome"+---++The Health page brings together system, run, and queue health so you can determine whether a problem is coming from your infrastructure, or individual flows.++## **System Health**++Use System Health to check whether the app and workers running Activepieces are healthy.++Activepieces checks areas such as version, release integrity, disk, RAM, and CPU and highlights anything that needs attention.++It also shows Daily job health for the last 30 days, so you can see whether platform jobs have been operating consistently over time.++If a system check needs attention, use the details shown for that check to determine which part of your deployment needs investigation.++## **Runs Health**++Use Runs Health to understand how reliably jobs are completing across your platform.++You can review job volume and success rate for a selected period and distinguish between successful, failed, cancelled, and internal-error jobs.++Internal errors are particularly useful when troubleshooting because they represent failures inside Activepieces, such as the engine or worker, rather than failures caused by your flow logic. Activepieces groups these errors by the projects and flows they affected so you can understand their impact.++## **Queue Health**++Use Queue Health to check whether jobs are moving through your execution queue normally.++It shows how many jobs are currently running or queued and highlights stuck jobs.++A growing queue or stuck jobs can help you identify execution problems that may require further investigation.++<br />diff --git a/docs/admin-guide/guides/templates.mdx b/docs/admin-guide/guides/templates.mdxindex 71e49e76ae2..d9ae0645bd6 100644--- a/docs/admin-guide/guides/templates.mdx+++ b/docs/admin-guide/guides/templates.mdx@@ -1,6 +1,9 @@---title: "Templates"-icon: "newspaper"+icon:+ name: "puzzle"+ style: "regular"+ library: "fontawesome"---Templates enable you to convert your most common automation into reusable resources. You can share that with people so they don’t have to build the same thing repeatedly.diff --git a/docs/admin-guide/guides/trigger-health.mdx b/docs/admin-guide/guides/trigger-health.mdxnew file mode 100644index 00000000000..7a4ef1e76bb--- /dev/null+++ b/docs/admin-guide/guides/trigger-health.mdx@@ -0,0 +1,21 @@+---+title: "Triggers"+icon:+ name: "circle-location-arrow"+ style: "regular"+ library: "fontawesome"+---++The Triggers page helps platform admins monitor the health and performance of triggers across the platform.++Use this page to identify integrations whose triggers may be failing or behaving unexpectedly, especially when the problem affects multiple flows or projects.++## **Monitor trigger health**++Trigger health is grouped by piece, allowing you to see whether problems are concentrated around a particular integration.++You can review:++- The number of trigger runs over the last 14 days.+- Recent trigger results.+- Trigger health over the last 24 hours, 7 days, and 14 days.diff --git a/docs/admin-guide/guides/usage.mdx b/docs/admin-guide/guides/usage.mdxnew file mode 100644index 00000000000..a982de5a76a--- /dev/null+++ b/docs/admin-guide/guides/usage.mdx@@ -0,0 +1,34 @@+---+title: "Usage"+icon:+ name: "chart-line"+ style: "regular"+ library: "fontawesome"+---++The **Usage** page gives platform admins a central place to understand how resources are being consumed across the platform.++At the top of the page, you can see your overall usage for:++- **Credits:** The number of credits used and the credit limit included in your plan.+- **Users:** The number of users on the platform and the user limit included in your plan.++If your plan does not have a limit for a resource, it is shown as **Unlimited**.++### **Credits Usage by Project**++The Project section breaks down credit usage across individual projects, making it easier to see where usage is coming from.++For each project, you can see:++- **AI Usage:** Credits used by AI-related activity.+- **Runs Usage:** Credits used by flow runs.+- **Total:** The total credits used by the project.++If credit usage increases, you can identify which projects are responsible for most of that usage.++You can change the time period to review usage over a specific date range.++To understand the credit usage break down, checkout the Billing and Subscription page in the platform admin++<br />diff --git a/docs/admin-guide/guides/workers.mdx b/docs/admin-guide/guides/workers.mdxnew file mode 100644index 00000000000..3d351c3c605--- /dev/null+++ b/docs/admin-guide/guides/workers.mdx@@ -0,0 +1,29 @@+---+title: "Workers"+icon:+ name: "toggle-off"+ style: "regular"+ library: "fontawesome"+---++The **Workers** page gives platform admins a central place to view the workers running your Activepieces flows and monitor their health and resource usage. A worker is responsible for executing flows.++The worker page on your platform admin is designed for monitoring your existing workers.++For information about configuring and operating workers, including worker sizing, scaling, concurrency, failure recovery, sandboxing, and network isolation, see the [**Workers documentation**](/install/architecture/workers).++## **Monitor worker health**++Each worker is displayed separately so you can see its current status and resource usage.++For each worker, you can view:++- **Status:** Whether the worker is currently online.+- **CPU:** How much processing capacity the worker is currently using.+- **RAM:** How much memory the worker is using.+- **Disk:** How much disk space is being used.+- **Last seen:** How recently Activepieces received a health update from the worker.++You can use this information to quickly check whether your workers are online and identify workers experiencing unusually high resource usage.++<br />diff --git a/docs/docs.json b/docs/docs.jsonindex 066a93b7652..783eb4d19a4 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -126,7 +126,9 @@"flows/publishing-flows","flows/flow-approvals","flows/debugging-runs",- "flows/versioning"+ "flows/versioning",+ "flows/template-library",+ "flows/canvas-controls"]},{@@ -339,129 +341,139 @@"tab": "Enterprise Control","icon": "crown","groups": [- {- "group": "Overview",- "pages": [- "admin-guide/overview"- ]- },{- "group": "Guides",+ "group": "Overview","pages": [- {- "group": "General",- "pages": [- "admin-guide/guides/structure-projects",- "admin-guide/guides/project-releases",- "admin-guide/guides/project-replace-cli",- "admin-guide/guides/manage-concurrency",- "admin-guide/guides/permissions",- {- "group": "SCIM",- "icon": "users",- "pages": [- "admin-guide/guides/scim/overview",- "admin-guide/guides/scim/providers/okta",- "admin-guide/guides/scim/providers/microsoft-entra-id"- ]- },- "admin-guide/guides/connections"- ]- },- {- "group": "Setup",- "pages": [- "admin-guide/guides/general",- "admin-guide/guides/setup-ai-providers",- "admin-guide/guides/ai-capabilities",- "admin-guide/guides/global-connections",- "admin-guide/guides/manage-pieces",- "admin-guide/guides/templates"- ]- },- {- "group": "Observability",- "pages": [- {- "group": "Audit Logs",- "icon": "book",- "pages": [- "admin-guide/security/audit-logs/overview",- "admin-guide/security/audit-logs/flow-created",- "admin-guide/security/audit-logs/flow-updated",- "admin-guide/security/audit-logs/flow-deleted",- "admin-guide/security/audit-logs/flow-published",- "admin-guide/security/audit-logs/flow-activated",- "admin-guide/security/audit-logs/flow-deactivated",- "admin-guide/security/audit-logs/connection-upserted",- "admin-guide/security/audit-logs/connection-deleted",- "admin-guide/security/audit-logs/flow-run-started",- "admin-guide/security/audit-logs/flow-run-finished",- "admin-guide/security/audit-logs/agent-action-executed",- "admin-guide/security/audit-logs/folder-created",- "admin-guide/security/audit-logs/folder-updated",- "admin-guide/security/audit-logs/folder-deleted",- "admin-guide/security/audit-logs/user-signed-in",- "admin-guide/security/audit-logs/user-signed-up",- "admin-guide/security/audit-logs/user-email-verified",- "admin-guide/security/audit-logs/user-password-reset",- "admin-guide/security/audit-logs/signing-key-created"- ]- },- "admin-guide/guides/event-streaming"- ]- }+ "admin-guide/overview"]},{- "group": "Security",- "pages": [- "admin-guide/guides/sso",- {- "group": "Secret Managers",- "icon": "key",- "pages": [- "admin-guide/guides/secret-managers/overview",- "admin-guide/guides/secret-managers/aws",- "admin-guide/guides/secret-managers/hashicorp",- "admin-guide/guides/secret-managers/cyberark-conjur",- "admin-guide/guides/secret-managers/onepassword"- ]- },- "admin-guide/security/practices",- "admin-guide/guides/manage-oauth2",- {+ "group": "Guides",+ "pages": [+ {+ "group": "General",+ "pages": [+ "admin-guide/guides/structure-projects",+ "admin-guide/guides/project-releases",+ "admin-guide/guides/project-replace-cli",+ "admin-guide/guides/manage-concurrency",+ "admin-guide/guides/permissions",+ {+ "group": "SCIM",+ "icon": "users",+ "pages": [+ "admin-guide/guides/scim/overview",+ "admin-guide/guides/scim/providers/okta",+ "admin-guide/guides/scim/providers/microsoft-entra-id"+ ]+ },+ "admin-guide/guides/connections"+ ]+ },+ {+ "group": "Setup",+ "pages": [+ "admin-guide/guides/general",+ "admin-guide/guides/setup-ai-providers",+ "admin-guide/guides/ai-capabilities",+ "admin-guide/guides/global-connections",+ "admin-guide/guides/manage-pieces",+ "admin-guide/guides/templates",+ "admin-guide/guides/usage",+ "admin-guide/guides/embedding"+ ]+ },+ {+ "group": "Security",+ "pages": [+ "admin-guide/guides/sso",+ {+ "group": "Secret Managers",+ "icon": "key",+ "pages": [+ "admin-guide/guides/secret-managers/overview",+ "admin-guide/guides/secret-managers/aws",+ "admin-guide/guides/secret-managers/hashicorp",+ "admin-guide/guides/secret-managers/cyberark-conjur",+ "admin-guide/guides/secret-managers/onepassword"+ ]+ },+ "admin-guide/security/practices",+ "admin-guide/guides/manage-oauth2",+ {"group": "Audit Logs","icon": "book","pages": [- "admin-guide/security/audit-logs/overview",- "admin-guide/security/audit-logs/flow-created",- "admin-guide/security/audit-logs/flow-updated",- "admin-guide/security/audit-logs/flow-deleted",- "admin-guide/security/audit-logs/flow-published",- "admin-guide/security/audit-logs/flow-activated",- "admin-guide/security/audit-logs/flow-deactivated",- "admin-guide/security/audit-logs/flow-approval-requested",- "admin-guide/security/audit-logs/flow-approval-granted",- "admin-guide/security/audit-logs/flow-approval-rejected",- "admin-guide/security/audit-logs/flow-approval-withdrawn",- "admin-guide/security/audit-logs/connection-upserted",- "admin-guide/security/audit-logs/connection-deleted",- "admin-guide/security/audit-logs/flow-run-started",- "admin-guide/security/audit-logs/flow-run-finished",- "admin-guide/security/audit-logs/agent-action-executed",- "admin-guide/security/audit-logs/folder-created",- "admin-guide/security/audit-logs/folder-updated",- "admin-guide/security/audit-logs/folder-deleted",- "admin-guide/security/audit-logs/user-signed-in",- "admin-guide/security/audit-logs/user-signed-up",- "admin-guide/security/audit-logs/user-email-verified",- "admin-guide/security/audit-logs/user-password-reset",- "admin-guide/security/audit-logs/signing-key-created"+ "admin-guide/security/audit-logs/overview",+ "admin-guide/security/audit-logs/flow-created",+ "admin-guide/security/audit-logs/flow-updated",+ "admin-guide/security/audit-logs/flow-deleted",+ "admin-guide/security/audit-logs/flow-published",+ "admin-guide/security/audit-logs/flow-activated",+ "admin-guide/security/audit-logs/flow-deactivated",+ "admin-guide/security/audit-logs/flow-approval-requested",+ "admin-guide/security/audit-logs/flow-approval-granted",+ "admin-guide/security/audit-logs/flow-approval-rejected",+ "admin-guide/security/audit-logs/flow-approval-withdrawn",+ "admin-guide/security/audit-logs/connection-upserted",+ "admin-guide/security/audit-logs/connection-deleted",+ "admin-guide/security/audit-logs/flow-run-started",+ "admin-guide/security/audit-logs/flow-run-finished",+ "admin-guide/security/audit-logs/agent-action-executed",+ "admin-guide/security/audit-logs/folder-created",+ "admin-guide/security/audit-logs/folder-updated",+ "admin-guide/security/audit-logs/folder-deleted",+ "admin-guide/security/audit-logs/user-signed-in",+ "admin-guide/security/audit-logs/user-signed-up",+ "admin-guide/security/audit-logs/user-email-verified",+ "admin-guide/security/audit-logs/user-password-reset",+ "admin-guide/security/audit-logs/signing-key-created"]- }- ]- }+ }+ ]+ },+ {+ "group": "Observability",+ "pages": [+ {+ "group": "Audit Logs",+ "icon": "book",+ "pages": [+ "admin-guide/security/audit-logs/overview",+ "admin-guide/security/audit-logs/flow-created",+ "admin-guide/security/audit-logs/flow-updated",+ "admin-guide/security/audit-logs/flow-deleted",+ "admin-guide/security/audit-logs/flow-published",+ "admin-guide/security/audit-logs/flow-activated",+ "admin-guide/security/audit-logs/flow-deactivated",+ "admin-guide/security/audit-logs/connection-upserted",+ "admin-guide/security/audit-logs/connection-deleted",+ "admin-guide/security/audit-logs/flow-run-started",+ "admin-guide/security/audit-logs/flow-run-finished",+ "admin-guide/security/audit-logs/agent-action-executed",+ "admin-guide/security/audit-logs/folder-created",+ "admin-guide/security/audit-logs/folder-updated",+ "admin-guide/security/audit-logs/folder-deleted",+ "admin-guide/security/audit-logs/user-signed-in",+ "admin-guide/security/audit-logs/user-signed-up",+ "admin-guide/security/audit-logs/user-email-verified",+ "admin-guide/security/audit-logs/user-password-reset",+ "admin-guide/security/audit-logs/signing-key-created"+ ]+ },+ "admin-guide/guides/event-streaming"+ ]+ },+ {+ "group": "Infrastructure",+ "pages": [+ "admin-guide/guides/workers",+ "admin-guide/guides/health",+ "admin-guide/guides/trigger-health"+ ]+ }+ ]+ }]},{diff --git a/docs/flows/building-flows.mdx b/docs/flows/building-flows.mdxindex 139b3d6d30b..e16cceecf19 100644--- a/docs/flows/building-flows.mdx+++ b/docs/flows/building-flows.mdx@@ -7,10 +7,12 @@ description: "Flow consists of two parts, trigger and actions"The flow's starting point determines its frequency of execution. There are various types of triggers available, such as Schedule Trigger, Webhook Trigger, or Event Trigger based on specific service.+<video src="https://cdn.activepieces.com/videos/docs/triggers.mp4" controls />+## ActionActions come after the flow and control what occurs when the flow is activated, like running code or communicating with other services.-In real-life scenario:+Here is an example:-\ No newline at end of file+diff --git a/docs/flows/canvas-controls.mdx b/docs/flows/canvas-controls.mdxnew file mode 100644index 00000000000..d687486238e--- /dev/null+++ b/docs/flows/canvas-controls.mdx@@ -0,0 +1,60 @@+---+title: "Builder Canvas Controls"+icon: "gamepad-alt"+---++The Builder includes several controls that make it easier to navigate the canvas, change how your flow is displayed, and work with your steps.++### **Mini Map**++The **Mini Map** gives you an overview of your entire flow and lets you quickly move to different parts of it. This is especially useful when working with large flows that have many steps.++<video src="https://cdn.activepieces.com/videos/docs/maps.mp4" controls />++### **Zoom in and Zoom out**++Use **Zoom in** and **Zoom out** to adjust how much of your flow you can see on the canvas.++++### **Fit to view**++This automatically adjusts the canvas so your entire flow fits on the screen.++<video src="https://cdn.activepieces.com/videos/docs/fit-to-view.mp4" controls />++### **Image Download**++Use this to save an image of your flow.++++### **Layout Switch**++Use this to change how your flow is displayed. You can switch between a **vertical** and **horizontal** layout.++<video src="https://cdn.activepieces.com/videos/docs/vertical-horizontal.mp4" controls />++### **Grab Mode**++Use **Grab Mode** (hand icon) to grab the canvas and move around your flow.++<video src="https://cdn.activepieces.com/videos/docs/grab.mp4" controls />++### **Select Mode**++Use **Select Mode** (cursor icon) to select multiple steps at once.++Once selected, you can perform actions on the selected steps together, such as copying, skipping (which means that step will not be carried out in the flow), or deleting them.++<video src="https://cdn.activepieces.com/videos/docs/select.mp4" controls />++### **Notes**++Use **Notes** to add extra context directly to your flow.++Notes are especially useful when collaborating with other people. You can explain why a particular decision was made, provide context about a step, or leave information that someone else may need when working on the flow.++They can also help you remember why you made certain decisions when you return to a flow later.++<video src="https://cdn.activepieces.com/videos/docs/notes.mp4" controls />diff --git a/docs/flows/debugging-runs.mdx b/docs/flows/debugging-runs.mdxindex bbb3fdcc6e5..e144df704a6 100755--- a/docs/flows/debugging-runs.mdx+++ b/docs/flows/debugging-runs.mdx@@ -8,8 +8,11 @@ You can monitor each run that results from an enabled flow:1. Go to the Dashboard, click on **Runs**.2. Find the run that you're looking for, and click on it.-3. You will see the builder in a view-only mode, each step will show a ✅ or a ❌ to indicate its execution status.+3. You will see the builder in a view-only mode, each step will show succeeded or failed to indicate its execution status.4. Click on any of these steps, you will see the **input** and **output** in the **Run Details** panel.The debugging experience looks like this:-\ No newline at end of file++++<video src="https://cdn.activepieces.com/videos/docs/debugging.mp4" controls />diff --git a/docs/flows/passing-data.mdx b/docs/flows/passing-data.mdxindex 3c6c15c3350..a514d327807 100755--- a/docs/flows/passing-data.mdx+++ b/docs/flows/passing-data.mdx@@ -6,18 +6,13 @@ description: "Using data from previous steps in the current one"## Data flow-Any Activepieces flow is a vertical diagram that **starts with a trigger step** followed by **any number of action steps**.+Any Activepieces flow can either have a vertical or horizontal layout that starts with a trigger step followed by any number of action steps.-Steps are connected vertically. Data flows from parent steps to the children. Children steps have access to the output data of the parent steps.+Data flows from parent steps to the children (Children steps have access to the output data of the parent steps)## Example Steps-<video width="450"- autoPlay- muted- loop- playsinline- src="/resources/passing-data-3steps.mp4"-></video>++<video src="https://cdn.activepieces.com/videos/docs/data-flow.mp4" controls />This flow has 3 steps, they can access data as follows:@@ -29,57 +24,45 @@ This flow has 3 steps, they can access data as follows:## Data to Insert Panel-In order to use data from a previous step in your current step, place your cursor in any input, the **Data to Insert** panel will pop up.+In order to use data from a previous step in your current step, place your cursor in any input, the **Data selector** panel will pop up.-<video- autoPlay- muted- loop- playsinline- src="/resources/passing-data-data-to-insert-panel.mp4"-></video>+<video src="https://cdn.activepieces.com/videos/docs/insert-panel.mp4" controls />This panel shows the accessible steps and their data. You can expand the data items to view their content, and you can click the items to insert them in your current settings input.-If an item in this panel has a caret (⌄) to the right, it means you can click on the item to expand its child properties. You can select the parent item or its properties as you need.+If an item in this panel has a caret **(›)** to the right, it means you can click on the item to expand its child properties. You can select the parent item or its properties as you need.When you insert data from this panel, it gets inserted at the cursor's position in the input. This means you can combine static text and dynamic data in any field.-<video- autoPlay- muted- loop- playsinline- src="/resources/passing-data-main-insert-data-example.mp4"-></video>+<video src="https://cdn.activepieces.com/videos/docs/passing-data.mp4" controls />We generally recommend that you expand the items before inserting them to understand the type of data they contain and whether they're the right fit to the input you're filling.-## Testing Steps to Generate Data+## Testing Steps++While building flows, we require you to test each step you add before moving to the next step.++This enables you to access the data in the previous step and use it in the next step++This approach protects you from selecting the wrong data and breaking your flows after publishing them.-We require you to test steps before accessing their data. This approach protects you from selecting the wrong data and breaking your flows after publishing them.+If a tigger or a step is not tested , you will see a **Test me** on top of it. Click that step to open the side bar and test the step.-If a step is not tested and you try to access its data, you will see the following message:-<img width="350" src="/resources/passing-data-test-step-first.png" alt="Test your automation step first" />+For triggers here is what it looks like:-To fix this, go to the step and use the Generate Sample Data panel to test it. Steps use different approaches for testing. These are the common ones:+-- **Load Data:** Some triggers will let you load data from your connected account without having to perform any action in that account.-- **Test Trigger:** Some triggers will require you to head to your connected account and fire the trigger in order to generate sample data.-- **Send Data:** Webhooks require you to send a sample request to the webhook URL to generate sample data.-- **Test Action:** Action steps will let you run the action in order to generate sample data.+For actions or other steps, here is what it looks like:-Follow the instructions in the Generate Sample Data panel to know how your step should be tested. Some triggers will also let you Use Mock Data, which will generate static sample data from the piece. We recommend that you test the step instead of using mock data.+-This is an example for generating sample data for a trigger using the **Load Data** button:+To fix this, go to the step and use the **Test Step** button to test it.-<video- autoPlay- muted- loop- playsinline- src="/resources/passing-data-load-data.mp4"-></video>+Follow the instructions to know how your step should be tested.++This is an example of how your steps are tested:++<video src="https://cdn.activepieces.com/videos/docs/test.mp4" controls />## Advanced Tips@@ -87,13 +70,7 @@ This is an example for generating sample data for a trigger using the **Load DatDropdowns and some other input types don't let you select data from previous steps. If you'd like to bypass this and use data from previous steps instead, switch the input into a dynamic one using this button:-<video- autoPlay- muted- loop- playsinline- src="/resources/passing-data-dynamic-value.mp4"-></video>+<video src="https://cdn.activepieces.com/videos/docs/dynamic-values.mp4" controls />### Working with large files@@ -112,6 +89,8 @@ If you can't find the data you're looking for in the **Data to Insert** panel buUse the following syntax to write JSON paths:-`{{step_slug.path.to.property}}`+`{{step_name['output']['path']['to']['property']}}`++The easiest way to get the `step_name['output']` part right is to right-click the step on the canvas and select **Copy reference**. This copies `{{step_name['output']}}`to your clipboard, ready to extend with the rest of the path.-The `step_slug` can be found by moving your cursor over any of your flow steps, it will show to the right of the step.\ No newline at end of file+diff --git a/docs/flows/template-library.mdx b/docs/flows/template-library.mdxnew file mode 100644index 00000000000..e44e21a5c80--- /dev/null+++ b/docs/flows/template-library.mdx@@ -0,0 +1,48 @@+---+title: "Template Library"+---++The Template Library gives you ready-made automation flows that you can use instead of building a flow from scratch. You can customize them to fit your specific needs.++Templates cover common workflows across areas like Sales, Marketing, Customer Service, Finance, HR, Engineering, Operations, and AI Agents.++## **Find a template**++You can find the template library in the **Explore** tab.++Browse templates by category or search for a specific workflow using its name or description.++Each template gives you a quick overview of what the automation does and the apps it uses, so you can find a workflow that fits what you want to automate.++They also show an estimate of the time and cost they can save, helping you understand the potential value of automating that process.++++## **Preview a template**++Click on any template to see how the automation works before adding it to your project.++The template page shows:++- **About this template:** An overview of the process the template automates.+- **What's included:** The flows included in the template.+- **Used Pieces:** The apps and integrations required by the automation.+- **Flow preview:** A visual preview of the steps in the automation.+- **Setup guide:** Additional instructions for configuring the template, when available.++This lets you understand what the template does and what you'll need to connect before deciding to use it.++You can also check out what the flow looks like in the vertical or horizontal layout++<video src="https://cdn.activepieces.com/videos/docs/preview-template.mp4" controls />++## **Use a template**++When you find a template you want to use:++1. Open the template.+2. Review the flow and the pieces it uses.+3. Click **Use template** to start using the template+4. To learn more about the set up and how to connect your own credentials to use the template, click **Set Up Guide and** follow the setup instructions to configure the required connections and settings for your use case.++<br />diff --git a/docs/images/actions-and-triggers.png b/docs/images/actions-and-triggers.pngnew file mode 100644index 00000000000..07c6e595f72Binary files /dev/null and b/docs/images/actions-and-triggers.png differdiff --git a/docs/images/data-by-path.png b/docs/images/data-by-path.pngnew file mode 100644index 00000000000..9895c0e9ec3Binary files /dev/null and b/docs/images/data-by-path.png differdiff --git a/docs/images/image-download.png b/docs/images/image-download.pngnew file mode 100644index 00000000000..89f04743e9eBinary files /dev/null and b/docs/images/image-download.png differdiff --git a/docs/images/template-library.png b/docs/images/template-library.pngnew file mode 100644index 00000000000..f95c4cc499bBinary files /dev/null and b/docs/images/template-library.png differdiff --git a/docs/images/test-step-1.png b/docs/images/test-step-1.pngnew file mode 100644index 00000000000..e28236cd447Binary files /dev/null and b/docs/images/test-step-1.png differdiff --git a/docs/images/trigger-testing.png b/docs/images/trigger-testing.pngnew file mode 100644index 00000000000..0e853f9129bBinary files /dev/null and b/docs/images/trigger-testing.png differdiff --git a/docs/images/zoom.png b/docs/images/zoom.pngnew file mode 100644index 00000000000..b1fc4188db0Binary files /dev/null and b/docs/images/zoom.png differdiff --git a/docs/overview/welcome.mdx b/docs/overview/welcome.mdxindex 7c2355bb443..fee5736509b 100644--- a/docs/overview/welcome.mdx+++ b/docs/overview/welcome.mdx@@ -5,10 +5,12 @@ icon: "hand-wave"description: "AI automation for teams, with governance and security built in"---+Activepieces helps teams to build AI automation workflows, AI agents and ensure that your team actually uses AI in a way that is efficient with governance and security built in.+Describe what you want in chat, and Activepieces builds the agent or automation for you. Bring your own AI keys, run it on your own infrastructure, and keep the governance your company needs.<CardGroup cols={2}>- <Card href="https://cloud.activepieces.com/sign-up" title="Start free on Cloud" icon="cloud" color="#8143E3" horizontal>+ <Card title="Start free on cloud" color="#8143E3" icon="cloud" horizontal href="https://cloud.activepieces.com/sign-up">Nothing to set up or maintain.</Card><Card href="/install/overview" title="Self-host it" icon="server" color="#16A34A" horizontal>@@ -32,20 +34,26 @@ Mix them however you like. An agent can call a flow, a flow can run an agent, an</Card></CardGroup>+### **Apps**+Works where your team works. **760+ apps** and counting.+Your agent uses these apps to carry out tasks for you. These apps are also used to build flows based on what you want to achieve+<div style={{display:"flex",flexWrap:"wrap",gap:"0.7rem",marginTop:"1.25rem"}}><img noZoom src="https://cdn.activepieces.com/pieces/slack.png" alt="Slack" title="Slack" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/gmail.png" alt="Gmail" title="Gmail" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/google-sheets.png" alt="Google Sheets" title="Google Sheets" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/notion.png" alt="Notion" title="Notion" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/hubspot.png" alt="HubSpot" title="HubSpot" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/salesforce.png" alt="Salesforce" title="Salesforce" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/openai.png" alt="OpenAI" title="OpenAI" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/airtable.png" alt="Airtable" title="Airtable" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/github.png" alt="GitHub" title="GitHub" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /></div><div style={{display:"flex",flexWrap:"wrap",gap:"0.7rem",marginTop:"0.7rem"}}><img noZoom src="https://cdn.activepieces.com/pieces/stripe.png" alt="Stripe" title="Stripe" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/shopify.png" alt="Shopify" title="Shopify" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/discord.png" alt="Discord" title="Discord" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/microsoft-teams.png" alt="Microsoft Teams" title="Microsoft Teams" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/google-calendar.png" alt="Google Calendar" title="Google Calendar" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/google-drive.png" alt="Google Drive" title="Google Drive" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/linear.png" alt="Linear" title="Linear" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/asana.png" alt="Asana" title="Asana" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /><img noZoom src="https://cdn.activepieces.com/pieces/intercom.png" alt="Intercom" title="Intercom" style={{width:"44px",height:"44px",margin:0,padding:"7px",borderRadius:"11px",background:"#ffffff",border:"1px solid rgba(0,0,0,0.08)",objectFit:"contain",flexShrink:0}} /></div>## Build with AI+If you don't want to build flows manually, AI can build it for you. All you need to do is describe what you want.+<CardGroup cols={2}><Card href="/ai/chat" title="Chat" icon="message" color="#8143E3">Describe the outcome and Chat builds the flow. **Beta**</Card><Card href="/mcp/overview" title="MCP server" icon="plug" color="#0EA5E9">- Build from your own AI client.+ Build from your own AI client after connecting them to Activepieces</Card></CardGroup>