CodeWords

More than 3,000 integrations connect through OAuth from the Integrations settings, among them Gmail, Outlook, Google Sheets, Drive and Calendar, Notion, Slack, HubSpot, Airtable, Shopify, GitHub and Instagram, with separate Work and Personal accounts for the same app.

Any other service joins through API keys stored securely and used inside workflows, and built in services cover Firecrawl scraping, Redis storage and LinkedIn messaging through the user's session.

Because Cody writes real code for each workflow, an automation can read a lead from a form, enrich it, create the HubSpot record and message the owner on Slack in one run.

Sourcedocs.codewords.ai/help-center/billing/integrations.mdread 2026-10-18

Cody switches on its own between chat, plan, build and debug modes: complex requests with several integrations get a plan laid out as a todo list, then Cody writes the service code, configures tool connections, registers triggers, tests each stage and deploys.

The result is a multistep workflow shown as a graph of nodes, from trigger through each step and integration to the output, with the code view behind it. AI agent services built this way combine several tools, a persona and their own triggers, and when Cody stays blocked after repeated attempts it pauses, explains and asks how to proceed.

Sourcedocs.codewords.ai/automations/how-cody-works.mdread 2026-10-18

Workflows ground their output in live sources fetched at run time: Firecrawl scrapes websites into clean text and watches pages for changes, Perplexity supplies search grounded answers, and integrations read documents from Google Drive, Notion and Sheets. Cody itself researches with web search, documentation and page scraping before building. There is no knowledge base that indexes a company's documents for retrieval, and citations to stored sources are not part of the built agents unless Cody codes them.

Sourcedocs.codewords.ai/automations/firecrawl-for-web-scraping.mdread 2026-10-18

Oversight sits mostly at build time. Cody confirms requirements, shows its plan as a todo list that the user reviews, edits and approves before building, and asks for approval before a web app goes to production.

LinkedIn sends and posts require the account owner's approval and configured rate limits, WhatsApp conversations can be handed to a person with full context, and unverified booking requests are captured for later human confirmation.

Once a workflow is live, though, the builder offers no general approval step that pauses a run before a sensitive action, so any such gate has to be coded into the workflow by asking Cody for it.

Sourcedocs.codewords.ai/automations/the-building-process.mdread 2026-10-18

CodeWords is in the process of obtaining a SOC 2 Type II report and holds no completed attestation or certification yet.

Data is encrypted at rest and in transit on AWS, each run executes in an isolated sandbox that is destroyed when it finishes, Cody collects credentials through a secure flow instead of chat text, and internal access reviews, data classification and retention policies are in place, with a DPA available.

On the customer side, workspaces organize work into projects and folders and workflows can be shared by link, but there are no roles, team permissions or single sign on for deciding who in a company can build, edit or run an automation.

Sourcedocs.codewords.ai/security.mdread 2026-10-18

Activity brings past chats, workflow runs, scheduled runs and triggers into one view, with runs searchable and sortable by date or cost and filterable by status and by whether a schedule, a person or a trigger started them. Each run page shows the step in progress as it updates, the output and the error details of a failed run. Usage breaks credit spend down by day, by chat and by workflow run, and the graph view and code view expose exactly what each automation does.

Sourcedocs.codewords.ai/automations/activity.mdread 2026-10-18

Cody builds a structured memory of each user from six sources: account basics, onboarding context, a live view of the user's workflows and how they perform, the names of connected services, behavioral patterns distilled from periodic reviews of conversations, and recent chat topics, each refreshed on its own schedule, with credentials never stored.

That summary lets Cody skip setup questions in new chats, and it can also search past conversations to recall earlier work. Inside deployed workflows, Redis stores and recalls data between runs, so a bot can remember what it already posted or who it already answered.

Sourcedocs.codewords.ai/automations/memory-in-codewords.mdread 2026-10-18

Workflows run only in CodeWords' managed cloud on AWS, each in a sandbox created for the run and destroyed afterward. CodeWords says plainly that engineering teams wanting to self host the runtime are not the audience it builds for, and buyers get no choice of hosting region or data residency option. Web apps built on CodeWords can be exported to the customer's own GitHub repository, and the code behind each automation belongs to the customer, but automations themselves stay on the managed platform and cannot be moved into a company's own cloud.

Sourcecodewords.ai/llms.txtread 2026-10-18

More than 876 ready templates can be remixed instead of built from scratch, grouped by job across analytics, sales, marketing, support, operations, finance and more, from a competitor news monitor and customer feedback analyzer to trading signal bots and daily market briefings. WhatsApp alone has more than 125 templates for personal assistants, group bots and lead qualification, Business plans add a set of business templates, and Cody adapts any template to a team's own tools by conversation.

Sourcecodewords.ai/templates/llms.txtread 2026-10-18

Schedules run a workflow once or on a recurring timetable in the user's timezone, with optional email confirmations, and triggers start one on Slack messages, reactions or channel joins, WhatsApp DMs, group messages and reactions, new Gmail emails, label changes or drafts, and Google Calendar events.

Webhooks give each workflow or agent an HTTP endpoint for outside systems, the API runs workflows synchronously or asynchronously with file uploads, and runs can also start from chat or a run page. On WhatsApp, a workflow can answer on the customer's own number through the personal device route without a Meta Business API application.

Sourcedocs.codewords.ai/automations/schedules-and-triggers.mdread 2026-10-18

Workflows can use Anthropic's Claude Opus, Sonnet and Haiku, OpenAI's GPT 5, GPT 4.1, o3 and o4 mini, Google Gemini with Imagen 4 for images and Veo for video, and Perplexity for search grounded answers, with Cody choosing the model and wiring the calls. Users can ask Cody to switch a step to a cheaper model to cut credit use, and any other model provider can be reached through its API key. Templates name the model they run on, such as GPT 4.1 or Claude Sonnet 4.5.

Sourcedocs.codewords.ai/llms-full.txtread 2026-10-18

Paid plans get a CodeWords API key for calling workflows from outside, synchronously or asynchronously with file uploads, alongside webhook endpoints and an OpenAPI description on the developer pages. An MCP server lets Claude Code, Cursor, VS Code and other MCP clients build agents and automations on CodeWords, and the Claude connector and ChatGPT plugin let those assistants write the code, connect Slack, Gmail or Notion, deploy, schedule runs, read logs and fix a failed run without leaving the chat. Everything Cody builds is real code the customer owns.

Sourcedocs.codewords.ai/automations/calling-codewords-workflows.mdread 2026-10-18

Cody tests integrations and APIs before building, tests each stage as it builds and fixes errors on its own, and a debug mode takes over when a user reports a broken workflow. Triggers can be tested with real or sample data, the graph view shows which stages passed, and version history previews and restores earlier versions of an automation. There are no saved test sets, scored evaluations of an agent's answers or comparisons between versions.

Sourcedocs.codewords.ai/automations/how-cody-works.mdread 2026-10-18

The Web Agent is a cloud browser that works like a person, navigating pages, clicking buttons, filling forms, scrolling to load content and working behind logins, while the user watches through a live browser view or comes back to the results. The Chrome extension runs tasks inside the user's own logged in browser for private pages such as LinkedIn feeds and dashboards, including clicks and form fills on scheduled runs, with a five minute limit per run. Cody chooses between the Web Agent and Firecrawl depending on whether a page needs interaction.

Sourcedocs.codewords.ai/features/web-agent.mdread 2026-10-18