# ModuleX

> ModuleX is an AI workflow platform. Describe a process in plain English, open the graph it builds, and publish a workflow that runs across 179+ integrations.

ModuleX connects AI agents to 179 integrations (1,784 actions). Describe a process in plain English; an agent picks the right tool or the composer assembles a repeatable workflow you can run from chat, API, SDK, or triggers. Integrations run on your organization’s own credentials.

## Product
- [Sign up](https://app.modulex.dev/auth/sign-up): free plan, no credit card
- [App](https://app.modulex.dev)
- [Documentation](https://docs.modulex.dev)
- [Pricing](https://modulex.dev/pricing): machine-readable at https://modulex.dev/pricing.md
- [Credential vault](https://modulex.dev/product/credential-vault): ModuleX stores your OAuth grants and API keys once for the organization, encrypted. Agents act with them without ever seeing them, and every run is attributed.
- [AI Composer](https://modulex.dev/product/ai-composer): The ModuleX AI Composer turns a plain-language description into an editable workflow on the visual canvas, node by node, so you can review and change every step.
- [Knowledge bases](https://modulex.dev/product/knowledge-bases): ModuleX provides managed knowledge bases with ModuleX-managed vector storage (modulexdb), or connect your own Qdrant, Pinecone, MongoDB Atlas, or Weaviate.

## Integrations (179 tools, 1,784 actions)
- [Full catalog](https://modulex.dev/integrations)
- [Productivity & Collaboration (21)](https://modulex.dev/integrations/category/productivity-collaboration): Docs, notes, wikis and shared workspaces an agent can read, update and keep in sync as work happens.
- [Developer Tools & Infrastructure (19)](https://modulex.dev/integrations/category/developer-tools-infrastructure): Source control, CI, package registries and deploy targets an agent can drive straight from a request.
- [Marketing & Advertising (17)](https://modulex.dev/integrations/category/marketing-advertising): Campaign, email, ads and content platforms an agent can launch, adjust and report on from plain English.
- [Sales (15)](https://modulex.dev/integrations/category/sales): Pipeline, outreach and enrichment tools an agent can move deals through without you opening a tab.
- [Communication (14)](https://modulex.dev/integrations/category/communication): Email, chat and messaging channels an agent can read, draft into and post to on your behalf.
- [Analytics & Data (9)](https://modulex.dev/integrations/category/analytics-data): Product, web and event analytics an agent can query to answer "what happened" without a dashboard.
- [Finance & Payments (9)](https://modulex.dev/integrations/category/finance-payments): Payments, billing and accounting systems an agent can run charges, invoices and subscriptions against.
- [Web Search & Scraping (9)](https://modulex.dev/integrations/category/web-search-scraping): Search, crawl and extraction APIs an agent can use to pull live facts and structured data off the web.
- [AI & Machine Learning (8)](https://modulex.dev/integrations/category/ai-machine-learning): Models, embeddings and inference providers an agent can call as steps inside a larger task.
- [Monitoring & Observability (8)](https://modulex.dev/integrations/category/monitoring-observability): Metrics, logs and incident tools an agent can watch, query and act on when something breaks.
- [Cloud Infrastructure (7)](https://modulex.dev/integrations/category/cloud-infrastructure): Compute, storage and platform providers an agent can provision and operate from a description.
- [E-Commerce (7)](https://modulex.dev/integrations/category/e-commerce): Storefronts and order systems an agent can manage products, inventory and fulfillment across.
- [CRM (6)](https://modulex.dev/integrations/category/crm): Contact and account systems an agent can read, enrich and update as relationships change.
- [Project & Task Management (6)](https://modulex.dev/integrations/category/project-task-management): Issue trackers and boards an agent can create, triage and move work through end to end.
- [Scheduling & Events (6)](https://modulex.dev/integrations/category/scheduling-events): Calendars and booking tools an agent can check availability on, schedule and reschedule across.
- [Social Media (6)](https://modulex.dev/integrations/category/social-media): Social platforms an agent can publish to, monitor and pull engagement from on a cadence.
- [Databases (5)](https://modulex.dev/integrations/category/databases): SQL and managed datastores an agent can read from and write to as part of a task.
- [Vector Database (4)](https://modulex.dev/integrations/category/vector-database): Vector stores an agent can query and update for semantic search, retrieval and embedding-backed workflows.
- [Customer Support (2)](https://modulex.dev/integrations/category/customer-support): Ticketing and help-desk tools an agent can triage, draft replies in and resolve through.
- [Education (1)](https://modulex.dev/integrations/category/education): Learning platforms an agent can pull content, courses and progress from on demand.

## Integration pairings
- [Gmail + Notion](https://modulex.dev/integrations/gmail/with/notion)
- [HubSpot + Slack](https://modulex.dev/integrations/hubspot/with/slack)
- [Slack + Stripe](https://modulex.dev/integrations/slack/with/stripe)

## ModuleX MCP (use ModuleX from MCP clients)
- [ModuleX MCP for Claude Code](https://modulex.dev/claude-code): deployed workflows, Files, and Knowledge as MCP tools
- [ModuleX MCP for Cursor](https://modulex.dev/cursor): deployed workflows, Files, and Knowledge as MCP tools
- [ModuleX MCP for Codex](https://modulex.dev/codex): deployed workflows, Files, and Knowledge as MCP tools
- [ModuleX MCP for Hermes](https://modulex.dev/hermes): deployed workflows, Files, and Knowledge as MCP tools
- [ModuleX MCP for OpenClaw](https://modulex.dev/claw): deployed workflows, Files, and Knowledge as MCP tools

## Use cases
- [Daily Inbox Digest](https://modulex.dev/use-cases/daily-inbox-summary-to-notion): Every morning your team gets a clean digest of overnight email in Notion, without opening the inbox. A ModuleX agent reads the unread threads, summarizes them, and files a dated page in your Notion database.
- [Inbound Lead Routing](https://modulex.dev/use-cases/qualify-inbound-leads-to-slack): New leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.
- [Failed Payment Follow-up](https://modulex.dev/use-cases/failed-payment-follow-up): A failed invoice stops being a silent number on a dashboard and becomes a tracked case your team can act on. When Stripe reports a payment failure, a ModuleX agent pulls the details, re-sends the invoice, and posts the case to Slack.
- [Support Ticket Triage](https://modulex.dev/use-cases/triage-support-tickets-to-slack): New tickets get read, prioritized, and routed the moment they land, and the urgent ones surface in Slack instead of sitting in a queue. A ModuleX agent classifies each Freshdesk ticket, sets its priority and tags, assigns it, and posts the ones that cannot wait.
- [Grounded Support Replies](https://modulex.dev/use-cases/draft-support-replies-with-context): Every reply starts as a grounded draft that already knows the customer’s history, so agents edit instead of writing from scratch. A ModuleX agent reads the Intercom conversation and contact, drafts a reply, and leaves it as a note for a human to approve.
- [Adapt one announcement for each channel](https://modulex.dev/use-cases/adapt-one-post-for-each-channel): One announcement, rewritten per channel, reviewed in one place before anything goes out. Built for a one-person marketing team posting the same text everywhere.
- [Answer an order question with the order in hand](https://modulex.dev/use-cases/answer-order-questions): A reply that answers with the real order status instead of asking the customer for their order number. Built for an ecommerce team answering the same three questions about where a package is.
- [Answer support questions using your own documentation](https://modulex.dev/use-cases/answer-support-questions-from-your-docs): A drafted answer grounded in your own material, showing what it drew from, behind an approval step. Built for support teams whose answers already exist, just not where the question arrives.
- [Assemble the evidence pack for a review](https://modulex.dev/use-cases/assemble-an-evidence-pack): An evidence pack assembled from your systems, with the gaps named and assigned. Built for whoever collects the same screenshots and exports every audit cycle.
- [Book the meeting and log it against the deal](https://modulex.dev/use-cases/book-and-log-a-meeting): A booked meeting that is already recorded where your pipeline reporting will look for it. Built for a rep who books the call, then forgets to record it anywhere.
- [Brief yourself on a candidate before the call](https://modulex.dev/use-cases/brief-yourself-on-a-candidate): A brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.
- [Build a one-pager on a company before you meet them](https://modulex.dev/use-cases/build-a-company-one-pager): A one-pager combining public background with your own record, reusable by whoever meets them next. Built for anyone walking into a meeting knowing only the company name.
- [Capture a request as a task without leaving the thread](https://modulex.dev/use-cases/capture-a-request-as-a-task): A task that carries the original request and links back to where it was made. Built for anyone who says yes in an email and then forgets.
- [Catch up on a channel you stopped reading](https://modulex.dev/use-cases/catch-up-on-a-busy-channel): A summary of decisions and open questions, with the items waiting on you called out. Built for anyone returning to a busy channel after two days away.
- [Categorise card spend without the month-end scramble](https://modulex.dev/use-cases/categorise-card-spend): A categorised transaction list plus a short list of the entries that genuinely need a human. Built for a finance lead reconciling a month of transactions from memory.
- [Check database health without opening the dashboard](https://modulex.dev/use-cases/check-database-health): A short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.
- [Put an external MCP server to work](https://modulex.dev/use-cases/connect-an-mcp-server): A tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.
- [See which posts are actually being read](https://modulex.dev/use-cases/content-performance-digest): A digest that separates the pieces people found from the pieces they did not. Built for a content lead who publishes steadily and reviews performance rarely.
- [See which accounts went quiet this week](https://modulex.dev/use-cases/customer-health-digest): One weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.
- [Start the day with one brief instead of five tabs](https://modulex.dev/use-cases/daily-brief-across-your-tools): One brief covering the meetings, the messages that need a reply, and the work that is due. Built for anyone who begins the morning reconstructing the day from four apps.
- [Start the day knowing what moved in the repo](https://modulex.dev/use-cases/daily-repo-brief): A short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.
- [Turn a customer email into a tracked issue](https://modulex.dev/use-cases/email-to-tracked-issue): A tracked issue an engineer can pick up without opening the email, and a customer who knows it was logged. Built for support and product teams where bug reports die in an inbox.
- [Enrich a new lead before anyone calls it](https://modulex.dev/use-cases/enrich-a-new-lead): A lead record with the basics already filled in, and a note of where each field came from. Built for a sales team where half the inbound records arrive as a name and an email.
- [File meeting notes where someone will find them](https://modulex.dev/use-cases/file-meeting-notes-where-they-belong): A filed summary and real action items with owners, instead of a transcript nobody reopens. Built for a team whose notes are captured and then lost.
- [Get a first-pass review onto the pull request](https://modulex.dev/use-cases/first-pass-code-review): A first-pass review on the pull request while the author still has the change in their head. Built for a team where pull requests wait a day for anyone to look at them.
- [Fix what the SEO crawl actually found](https://modulex.dev/use-cases/fix-what-an-seo-crawl-found): A short ordered list of page-level fixes, each already written as a ticket. Built for a marketer holding a 200-row audit export and no idea which row matters.
- [Flag the campaigns that stopped working](https://modulex.dev/use-cases/flag-underperforming-campaigns): A short list of campaigns to act on, each with the numbers that put it there, and your approval in front of the change. Built for a growth lead who notices wasted spend a month late.
- [Draft a follow-up that knows where the deal stands](https://modulex.dev/use-cases/followup-with-deal-context): A short, context-aware reply waiting in your drafts, with the ask made explicit. Built for an account executive with a dozen replies to write between calls, and no time to re-read every thread.
- [Generate narration for a short video](https://modulex.dev/use-cases/generate-narration-for-a-video): Narration generated from the approved script, in the same place as the rest of the project. Built for a small team producing videos without a recording setup.
- [Import a contact list into your CRM without the cleanup](https://modulex.dev/use-cases/import-contacts-into-your-crm): Contacts in the CRM with the fields mapped, and a list of the rows that needed a human decision. Built for whoever inherits the spreadsheet after a conference.
- [Investigate an error spike while it is still spiking](https://modulex.dev/use-cases/investigate-an-error-spike): An investigation note that starts with a timeline instead of a blank page. Built for an on-call engineer who gets an alert and a blank page to start from.
- [Keep a personal spending tracker current](https://modulex.dev/use-cases/keep-a-spending-tracker-current): A tracker that stays current, with unfamiliar entries surfaced rather than guessed. Built for anyone whose budget sheet is accurate for the first week of the month.
- [Write the launch recap while the numbers are fresh](https://modulex.dev/use-cases/launch-recap-with-the-numbers): A recap with the numbers attached, written while people still remember the week. Built for a team that finishes a launch and never writes down how it went.
- [Assemble the month-end close digest](https://modulex.dev/use-cases/month-end-close-digest): A month-end digest in a consistent shape, assembled from the systems of record. Built for a finance team that rebuilds the same summary every month by hand.
- [Open an incident with the context already attached](https://modulex.dev/use-cases/open-an-incident-with-context): An incident that opens with a timeline and the relevant links already in it. Built for whoever is paged first and has to bring everyone else up to speed.
- [Plan the launch week's posts in one pass](https://modulex.dev/use-cases/plan-the-launch-week-posts): A week of posts with a deliberate arc, reviewed before the launch rather than during it. Built for whoever is running a launch and writing the posts the night before.
- [Draft the next sprint from the backlog you have](https://modulex.dev/use-cases/plan-the-next-sprint): A candidate list that people can argue with, ready before the meeting rather than during it. Built for a team that spends the first hour of planning finding the candidates.
- [Prepare everything a new joiner needs on day one](https://modulex.dev/use-cases/prepare-a-new-joiner-checklist): A per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.
- [Prepare an offer and send it for signature](https://modulex.dev/use-cases/prepare-an-offer-for-signature): An offer letter produced from the approved details, checked by a person, then sent for signature. Built for whoever assembles offer letters from a template and hopes the numbers are right.
- [Prepare for the next meeting in the gap before it](https://modulex.dev/use-cases/prepare-for-your-next-meeting): A short brief on who you are meeting, what was last agreed, and what is still open. Built for anyone with back-to-back calls and no preparation time between them.
- [Produce a short video from an existing piece](https://modulex.dev/use-cases/produce-a-short-video-cut): A short cut built from work you already published, reviewed before it goes out. Built for a team whose long-form content never becomes short-form.
- [Produce on-brand images for a set of posts](https://modulex.dev/use-cases/produce-on-brand-social-images): A consistent image set produced from your template and reviewed in one pass. Built for a marketer waiting on design for images that follow a fixed pattern.
- [Protect the time you actually need to work](https://modulex.dev/use-cases/protect-time-for-focused-work): Focus blocks on the calendar before the week fills, chosen by you from what was actually free. Built for anyone whose calendar fills with meetings before they can plan the week.
- [Get an approved draft onto the docs site](https://modulex.dev/use-cases/publish-to-your-docs-site): An approved draft turned into a docs change, ready for the normal review that already exists. Built for a team where finished documentation waits days for someone to publish it.
- [Reconcile payouts against your ledger](https://modulex.dev/use-cases/reconcile-payouts): A reconciliation summary that names the specific rows to look at, not just a total that is off. Built for whoever matches the payment processor to the accounting sheet each week.
- [Request the access a new joiner needs, with a person approving](https://modulex.dev/use-cases/request-access-for-a-new-joiner): An access request with an explicit approver and a written record of the decision. Built for an IT lead who grants access by message and remembers it later, if at all.
- [Research a question across sources at once](https://modulex.dev/use-cases/research-a-question-in-parallel): A summary that keeps public sources and internal material clearly apart, each cited. Built for anyone researching a decision with fifteen tabs and no notes.
- [Research and outline a piece before you write it](https://modulex.dev/use-cases/research-and-outline-a-piece): An outline where each section already carries the source it rests on, internal and external kept separate. Built for a writer who starts every article with twenty open tabs.
- [Route a purchase request to the right approver](https://modulex.dev/use-cases/route-a-purchase-request): A request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.
- [Schedule an interview panel without the thread](https://modulex.dev/use-cases/schedule-an-interview-panel): A workable slot found across the panel, with invitations drafted and waiting for your approval. Built for a recruiter coordinating four calendars and a candidate.
- [Send a short reply from a one-line instruction](https://modulex.dev/use-cases/send-a-short-reply-from-a-note): A short reply, in the right thread, waiting for your approval before it goes. Built for anyone who knows what to say but not who to say it to.
- [Ship the latest commit and watch the build](https://modulex.dev/use-cases/ship-the-latest-commit): A deploy that was confirmed by a person, watched to completion, and reported where the team reads. Built for a small team where deploying means remembering four steps in order.
- [Sort an inbox into actions, not folders](https://modulex.dev/use-cases/sort-the-inbox-into-actions): An inbox turned into a short list of actions, each linked back to the message it came from. Built for someone whose inbox is a to-do list with no order.
- [Turn an overnight inbox into a short list](https://modulex.dev/use-cases/summarise-an-overnight-inbox): A short digest that names the messages needing a reply and compresses everything else. Built for anyone who opens the laptop to fifty unread messages.
- [Find the pattern across a round of user interviews](https://modulex.dev/use-cases/synthesise-user-interviews): A themed synthesis where every theme points back to the interviews that produced it. Built for a product team with twelve interview transcripts and no time to reread them.
- [Keep a personal application pipeline in order](https://modulex.dev/use-cases/track-an-application-pipeline): A tracker whose stages match what actually happened in the inbox. Built for anyone tracking a search across a spreadsheet, an inbox, and memory.
- [Triage the engineering backlog into something readable](https://modulex.dev/use-cases/triage-the-engineering-backlog): A backlog where new issues carry a label and a priority, and the duplicates are surfaced. Built for a team lead whose backlog has become a place issues go to be forgotten.
- [Triage the support queue before your shift starts](https://modulex.dev/use-cases/triage-the-support-queue): A queue that is grouped and ordered, with repeated issues visible as one cluster. Built for a support lead who opens the queue to sixty tickets and no order to them.
- [Turn a finished design into tickets](https://modulex.dev/use-cases/turn-a-design-into-tickets): A set of tickets that map to the actual screens, each linked back to the design. Built for a product engineer who receives a design file and has to make it into work.
- [Turn a long post into an email sequence](https://modulex.dev/use-cases/turn-a-post-into-an-email-sequence): A drafted sequence, in order, waiting in your email tool for a human pass. Built for a marketer whose best article was sent once and never used again.
- [Notice a ranking drop in the same week it happens](https://modulex.dev/use-cases/watch-for-ranking-drops): A weekly digest that names the pages and queries that moved, while it is still recent. Built for an SEO owner who finds out about a drop from the quarterly review.
- [Get told before you sell out of something](https://modulex.dev/use-cases/watch-stock-levels): An alert naming the items that are running low, before the storefront says sold out. Built for a store operator who discovers a stockout from a customer complaint.
- [Get the ad numbers without opening the ads manager](https://modulex.dev/use-cases/weekly-ad-performance-digest): A weekly digest with the movement per campaign, without opening the ads manager. Built for a growth marketer who checks campaigns daily out of anxiety, not insight.
- [Watch the funnel without building a dashboard](https://modulex.dev/use-cases/weekly-funnel-digest): A weekly stage-by-stage view of the funnel, assembled from the tools you already run. Built for a founder who wants the funnel numbers without another BI project.
- [Write the sprint recap from what actually happened](https://modulex.dev/use-cases/write-the-sprint-recap): A recap grounded in the tracker rather than in what people remember. Built for whoever writes the recap on Friday from a half-remembered week.

## Guides
- [Best integrations for engineering teams](https://modulex.dev/guides/best-integrations-for-engineering-teams): The tools an engineering team should connect to ModuleX first, the actions each one actually exposes, and where the narrow ones still earn their place.
- [Best integrations for marketing teams](https://modulex.dev/guides/best-integrations-for-marketing-teams): The tools a marketing team should connect to ModuleX first, what the assistant can actually do inside each one, and the recipes that already chain them together.
- [How to connect your first tool](https://modulex.dev/guides/how-to-connect-your-first-tool): You don't have to plan your integrations up front. Ask for the work you actually want, and the assistant tells you what it needs access to — here's how that flow goes and how to choose the first tool well.
- [Best integrations for support teams](https://modulex.dev/guides/best-integrations-for-support-teams): The integrations a support team should connect to ModuleX first, and the real actions an agent can run inside each one.

## Articles (research)
- [1,784 actions, 62 verbs](https://modulex.dev/contents/1784-actions-62-verbs): Our catalog exposes 1,784 actions. Across 65 published task recipes, 62 of them get called — and two account for a quarter of every call. Here is what the used slice looks like.
- [Sixty-five tasks, forty-one tools](https://modulex.dev/contents/sixty-five-tasks-forty-one-tools): We built a library of 65 task recipes, then counted what went into them. The tasks we could describe turned out to be small: a median of two tools, four steps, and most with no schedule at all.
- [The anatomy of an agent tool catalog](https://modulex.dev/contents/anatomy-of-an-agent-tool-catalog): We exported the ModuleX integration registry and looked at its shape: how tools spread across categories, and why the median one exposes just 7 actions.

## Solutions
- [ModuleX for customer support](https://modulex.dev/solutions/customer-support): Give a ModuleX agent your Freshdesk, Intercom, and Slack credentials and it triages tickets, drafts replies from each customer’s history, and escalates bugs.
- [ModuleX for marketing](https://modulex.dev/solutions/marketing): Connect Notion, Google Analytics, Google Ads, Mailchimp, and Canva, and the ModuleX assistant turns briefs into drafts and campaigns into readable results.
- [ModuleX for engineering](https://modulex.dev/solutions/engineering): Connect GitHub, Linear, Sentry, and Vercel, and the ModuleX assistant briefs you on overnight changes, triages the backlog, and turns error spikes into tracked issues.

## Company
- [Blog](https://modulex.dev/blog)
- [Changelog](https://modulex.dev/changelog)
- [About](https://modulex.dev/about)
- [Contact sales](https://modulex.dev/contact-sales)

Integration data last updated: Jul 2026.