Gumloop vs Lindy (2026)

Connectors to Gmail, Salesforce, Slack, Notion and 150+ more, plus custom MCP servers, set what an agent can reach; tools can be restricted one by one, and skill scripts can call integrations from Python.

Connections span Gmail, Slack, Notion, HubSpot and 1,000+ tools plus any hosted MCP server, with a credentials vault, per-integration guardrails, an HTTP Request skill for anything uncatalogued and 500+ actions from a Pipedream partnership, though legacy material claims 3,000+ integrations.

Agents delegate to subagents, an Agent node puts an agent inside a workflow, and workflows supply branching, loops and reusable subflows; in Loop Mode each iteration starts a new conversation unless conversation IDs are tracked.

One agent plans and runs multi-step work across tools, with Routines and skills, but no branching, conditions, multiple agents or flow surface the customer configures is documented.

Plain-language schedules, app events and per-agent webhooks start agents, and an agent can create and manage its own triggers, including custom polling triggers validated in a sandbox.

Schedules through Routines, events such as a meeting ending or an unanswered email, and channels across Slack, iMessage and SMS, Gmail and the major meeting platforms are all included on every plan.

Company Brain keeps connected knowledge sources synced, attached whole or at file and folder level, and agents search it automatically when a question touches internal knowledge.

Recorded meetings filed into a searchable library of shareable folders give a maintained knowledge store, while answers across Slack history and connected tools come back with the underlying file or decision attached.

Agents edit and create their own skills after a correction and apply them in later conversations, with file-level version history; Gumloop says skills are not conversation memory and are reloaded when relevant.

Memory is a versioned plain-file system the customer can open, read and edit like a document, scoped personal or workspace, and skills keep demonstrated procedures for reuse across the team.

Agents raise approval and input requests, enterprise controls require human approval before expensive actions, and per-tool authorization, connector restrictions and budgets limit what an agent can do.

Anything with outside impact, such as sending an email or updating a ticket, waits for a named approver on every plan while read-only lookups from approved sources proceed, with per-integration guardrails and permissions the customer sets and revokes.

SOC 2 Type II and GDPR with a trust center, role- and attribute-based access, per-tool authorization, SCIM provisioning, centrally managed secrets and a live inventory of MCP servers in use.

SOC 2 Type II audited by Johanson Group with a Drata trust center that releases reports on request, per-integration permissions and encryption on every plan, and SSO and SCIM on Enterprise only.

Gumstack traces every tool call to a user, agent or service principal, keeps a live inventory of MCP servers in use, reaches agents running outside Gumloop, and tracks credit spend per agent and team.

Team files carry version history and the meeting library is searchable, but no logging, tracing or audit page is documented for the current product, and a per-run task view appears only in legacy builder documentation.

Managed SaaS, or deployment into the customer's own cloud as a VPC in the region of their choice, with Gumloop operating the full stack there; open-weight model inference runs through US-based providers under Zero Data Retention.

The security page says residency requirements are supported, but no region, selection control, VPC, on-premises, self-hosted or dedicated option is documented, so the product is managed SaaS only.

Skills ship as packaged folders that can be downloaded, uploaded and shared with Owner, Editor, Viewer and Use Only roles; an organization skill library can sync with a GitHub repository, and a template library covers common flows.

The product ships 40+ skills on every plan that the agent picks up on its own, and customers add their own by showing Lindy a task once, after which it is saved for the whole team.

Models from every major provider, chosen per agent from presets or the full list; every model in the agent picker supports tool calling, and open-weight models run through US-based providers under Zero Data Retention.

The customer picks a model per task from a multi-provider roster, with model selection listed as included on every plan and the changelog recording models added over time, such as Gemini 2.5 Flash-Lite for phone calls.

Gumloop documents an API to create agents, start chat sessions and trigger automations, with Python and JavaScript SDKs, a CLI, a Gumloop MCP and a webhook URL on each agent.

The webhook trigger takes bearer-token authenticated calls with a callback response and an HTTP Request skill calls outside APIs, but no SDK, client library or Lindy-published MCP server is documented, and the OpenAPI specification listed in the documentation index could not be read.

Evaluations score every completed agent interaction against criteria the customer sets, with per-criterion pass or fail and rationales, and can be backfilled when criteria change.

Neither the documentation index nor the pricing page's included capabilities list any test, preview, sandbox, evaluation or benchmarking surface, and routines and skills take effect directly with no documented dry run.

A Chrome extension records actions on any website and replays them as automations, including on sites with no API; a related web automation node appears to be access-gated.

Computer use is included on every plan: the vendor introduced it as Autopilot, giving the agent its own cloud computer to do what the user could when a tool is not otherwise reachable.