A Capsule MCP that writes as well as reads
131 nodes on Capsule CRM's API v2, covering 130 of the 132 operations Capsule documents. 67 read and 64 act, so an assistant or a scheduled workflow can create a contact, open an opportunity, move it along a pipeline, apply a track, write a note and close a project, not only look things up. One bearer token connects it, and Capsule's API is included on every plan including the free one.
What the Capsule MCP connector does
The Capsule CRM connector for Mattering Automations is 131 nodes on Capsule's API v2 at api.capsulecrm.com. Parties cover the people and organisations in the account. Opportunities, pipelines, milestones and lost reasons cover the sales side. Projects, boards and stages cover the work that happens after a deal is won. Tasks, task categories, tracks and track definitions cover what has to be done and when. History entries cover the notes and emails logged against a record. Custom fields, tags, activity types, custom titles, teams, users, goals, countries, currencies and REST hooks cover the account configuration everything else hangs off. Sixty seven nodes read and sixty four act, which covers 130 of the 132 operations Capsule documents. Two operations are deliberately not built, both file transfers: uploading an attachment sends raw bytes rather than JSON, which a canvas node has no file handle to provide, and downloading one returns the file itself, which the connector envelope would degrade to a truncated string. A note can still carry an attachment whose upload token came from elsewhere. The node count is higher than the operation count because Capsule's single party create endpoint is split into two nodes, one for people and one for organisations.
Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. The same nodes are also steps in a visual workflow, so the thing an agent helps you work out in a conversation can then run on a schedule with nobody present, chain with every other connector in the same workflow, and hold one credential in a shared workspace rather than in each person's local config.
Capsule ships an MCP server of its own and this page is not going to pretend otherwise. There are three vendor artefacts. Capsule announced a local MCP server in its developer changelog on 15 April 2026, available as a private beta, running as a Docker container on your own machine and giving MCP-compatible tools read-only access to parties, opportunities, tasks and projects. Its source is public at github.com/zestia/capsule-mcp-scala, Zestia Ltd being the company Capsule is a service of. And there is a hosted connector, published in Claude's own connector directory and installed from Customize then Connectors with your ordinary Capsule login, documented on Capsule's support site. It is a good product and worth using if it fits: it authenticates as you, inherits exactly the records your login can see, and needs no token anywhere.
Three differences are worth being exact about rather than hand waving at. The first is writing. Capsule's own documentation states that read access lets the MCP client view data in the CRM while write access is currently limited to updating Custom Fields, and its support page adds that Claude cannot rename a record, reassign its owner, or touch any other core field. This connector ships 64 action nodes, which is creating and updating parties, opportunities, projects, tasks, notes and the account configuration behind them, plus 16 deletes flagged as destructive. The second is plan reach. Capsule's hosted connector is listed as available on Growth, Advanced and Ultimate. Capsule's API is a tick in all five columns of Capsule's own plan table, Free included, so this connector runs on any Capsule account. The third difference is softer and it is the one that actually matters most of the time: a vendor MCP server is a chat surface, and this is a workflow surface that also happens to speak MCP.
The first thing to understand about Capsule's data model is that a party is not a contact. Capsule has no contact type. It has a party, which is either a person or an organisation, told apart by a type field, and the two kinds do not share a name field: a person carries firstName and lastName, an organisation carries name, and neither carries the other. A single list call returns both kinds interleaved. That is why creating is split into two nodes here, Capsule: Create Person and Capsule: Create Organisation, so each config panel offers the fields that kind actually has instead of ten fields half of which are always wrong. Reading and updating stay single nodes, because Capsule's update endpoint is a partial merge over whichever kind the id already is, and their field descriptions say which fields belong to which kind. Every party list sample on the canvas carries one person row and one organisation row, so the draggable output paths show both shapes rather than hiding half the account.
Capsule has two separate process hierarchies and confusing them is the likeliest mistake a new reader makes. Milestones belong to pipelines and are the sales side: an opportunity sits on a milestone, and the milestone is what decides which pipeline the deal is in. Stages belong to boards and are the project side: a project sits on a stage, and setting the stage is what places it on a board. They are not two names for one thing, they never mix, and the pickers in this connector group each one under its own parent, milestones by pipeline and stages by board. If you are looking for the stages on your sales pipeline, what you want is Capsule: List Milestones for Pipeline.
The four REST Hook nodes manage Capsule's own webhooks and are not Mattering triggers. What they do is register a target URL that Capsule will POST to when a party, project, opportunity, task or user changes, which is useful when you already run a receiver, and they let a workflow inspect and tidy the subscriptions an account is carrying. They do not make an automation start when something happens in Capsule. Two limits come straight from Capsule: an account holds at most 20 subscriptions, hooks must be managed by account administrators, and only registered applications authenticated through the full OAuth flow can subscribe or unsubscribe one, so a personal access token can list hooks but cannot create them. Capsule workflows here run on a schedule or on a trigger from somewhere else in the platform.
Capsule allows each user 4,000 requests per hour and returns the remaining count and the reset time on every successful call, answering 429 past it. Capsule's own advice for staying inside that is a one second delay between requests and, for keeping a local copy in step, the since parameter plus the deleted endpoints rather than repeated full reads. This connector encodes exactly that: Capsule: List Parties, Capsule: List Opportunities and Capsule: List Projects take since, and Capsule: List Deleted Parties, Capsule: List Deleted Opportunities and Capsule: List Deleted Projects are the companions that tell you what went away. Paging is by page number with no cursor and the nodes do not auto-paginate, so one node is one request and an unbounded walk never hides behind a single canvas step.
One connection, three surfaces
- Visual automations. Drag Capsule nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Capsule node, ready to drop on the canvas
131 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 67
Capsule: Get Account Site
Show which Capsule account the connected token belongs to: its subdomain, its display name and its URL. Takes no parameters. Useful for building links back into Capsule from a notification and for confirming an automation is pointed at the account somebody meant.
Capsule: Get Activity Type
Fetch one activity type by id, with its icon and its updateLastContacted flag.
Capsule: Get Current User
Show the user the connected token belongs to. Two uses: it is the cheapest way to confirm a credential works, and it tells an automation whose identity its writes will be attributed to when no owner is set, which for a shared connector credential is worth knowing before creating records.
Capsule: Get Custom Field
Fetch one custom field definition, including its options for a list type and its captureRule, which on party fields limits the field to people or to organisations only.
Capsule: Get Entry
Fetch one history entry by id. Branch on data.entry.type before reading it: note, email and task entries carry different fields.
Capsule: Get Goal
Fetch one goal by id, with its type, frequency, target value, date range and assignee.
Capsule: Get Lost Reason
Fetch one lost reason by id, with its includedForConversion flag.
Capsule: Get Milestone
Fetch one milestone by id, with its pipeline, probability, complete flag and stale threshold.
Capsule: Get Multiple Opportunities
Fetch up to ten opportunities in one request by passing their ids comma separated. Capsule answers 404 for the whole request if any single id is unknown.
Capsule: Get Multiple Parties
Fetch up to ten parties in one request by passing their ids comma separated. Worth using inside a loop that would otherwise spend ten of the account's 4,000 hourly requests. Capsule answers 404 for the WHOLE request if any one id is unknown, so it is a batch read for trusted ids rather than an existence check.
Capsule: Get Multiple Pipelines
Fetch up to ten pipelines in one request by passing their ids comma separated. Capsule answers 404 for the whole request if any single id is unknown.
Capsule: Get Multiple Projects
Fetch up to ten projects in one request by passing their ids comma separated. Capsule answers 404 for the whole request if any single id is unknown.
Capsule: Get Opportunity
Fetch one opportunity by id. The read only lastStageChangedAt and lastOpenMilestone fields are the ones worth knowing about: they answer how long has this sat where it is without keeping a history table on our side.
Capsule: Get Party
Fetch one party by id. The record may be a person or an organisation and the payload differs accordingly, so branch on data.party.type before reading a name. Answers 404 when no party has that id.
Capsule: Get Pipeline
Fetch one pipeline by id. The payload is just id, name and description; the milestones that make up the pipeline are a separate read, Capsule: List Milestones for Pipeline.
Capsule: Get Project
Fetch one project by id. status is OPEN or CLOSED and closedOn is read only, set by Capsule when the project closes rather than by an update.
Capsule: Get Project Board
Fetch one project board by id. The payload is id, name and description; its stages are a separate read, Capsule: List Stages for Board.
Capsule: Get Project Stage
Fetch one project stage by id, with the board it belongs to and its position in that board's sequence.
Capsule: Get REST Hook
Fetch one webhook subscription by id. Capsule makes a hook visible only to the registered application that subscribed it, so a different connection answers as though it does not exist. This manages a webhook INSIDE Capsule. It is not a Mattering trigger and it does not make an automation start when something happens in Capsule; the target URL is a receiver you already run.
Capsule: Get Tag Definition
Fetch one tag definition. dataTag tells you whether the tag carries custom fields of its own.
Capsule: Get Task
Fetch one task by id. hasTrack tells you whether the task was created by a track rather than by hand, which matters before deleting it: removing one task from a track leaves a gap in a sequence somebody designed.
Capsule: Get Task Category
Fetch one task category by id, with its colour.
Capsule: Get Team
Fetch one team by id. Ask for the memberships embed to list its members.
Capsule: Get Track
Fetch one applied track by id, with its generated tasks. direction is START_DATE, meaning trackDateOn is the anchor the task dates were counted forward from.
Capsule: Get Track Definition
Fetch one track template with its full ordered list of task definitions, their day offsets and their assignee rules.
Capsule: Get User
Fetch one user by id. Ask for the party embed to reach their email address and phone number, which live on the linked party record rather than on the user.
Capsule: List Activity Type Icons
List the icons an activity type can use. A fixed set defined by Capsule, the same on every account, so it never changes per customer. Takes no parameters. This exists mainly so the icon field on the activity type nodes can offer real choices instead of asking for a magic string.
Capsule: List Activity Types
List the activity types on the account. An activity type categorises a HISTORY ENTRY, which is what makes a note show as a Call or a Meeting on a record's timeline and what activity reporting counts. Capsule's built in types have NEGATIVE ids (Note is -1, Task completed is -4, Email sent is -5); custom types added on a paid plan have positive ones. This is the lister behind the activity type picker on Capsule: Create Note.
Capsule: List Additional Parties on Opportunity
List the extra contacts attached to an opportunity, which is how Capsule models a deal with several stakeholders. The MAIN party is not in this list; it is the party field on the opportunity itself. Rows are polymorphic parties like every other party read.
Capsule: List Additional Parties on Project
List the extra contacts attached to a project. The MAIN party is not in this list; it is the party field on the project itself. Rows are polymorphic parties.
Capsule: List Countries
List the country names Capsule accepts in a party's address, each with its ISO alpha-2, alpha-3 and numeric codes. The same list on every account. Worth calling before an import, because the address country field wants Capsule's NAME for the country rather than a code.
Capsule: List Currencies
List the ISO 4217 currency codes Capsule supports, with their symbols. The same list on every account. This is the lister behind every currency picker in the connector: opportunity value, goal target and user preference.
Capsule: List Custom Fields
List the custom field DEFINITIONS for one record type. This is the schema, not the values: a definition has a name, a type and for list types its options, and it may belong to a DataTag, in which case the fields only appear on records carrying that tag. Values live on the records and need the fields embed to come back at all. Definition ids are scoped per record type, so the same id can mean different fields under parties and under opportunities.
Capsule: List Custom Titles
List the CUSTOM person titles added to this account, such as Dr or Sir. Read the name carefully: this returns only what the account has added and NOT Capsule's built in titles, so a person whose title is Mr will not have that value appear here. That is why the title field on Capsule: Create Person is free text rather than a picker.
Capsule: List Deleted Opportunities
List opportunities deleted since a date, as id and deletedAt pairs, plus a restrictedOpportunities array for records hidden from this token rather than removed. The companion to List Opportunities with since when keeping a local copy in step. Takes no page or perPage.
Capsule: List Deleted Parties
List parties deleted since a date, as bare id and deletedAt pairs. This is the other half of a Capsule sync: List Parties with since tells you what changed, and this tells you what vanished, which no amount of re-reading the live collection will. The response also carries restrictedParties when records were made invisible to this token rather than deleted, and those look identical from the outside, so treat both as gone for this user. Note the endpoint takes no page or perPage.
Capsule: List Deleted Projects
List projects deleted since a date, as id and deletedAt pairs. The companion to List Projects with since when keeping a local copy in step. Takes no page or perPage.
Capsule: List Entries
Read the whole account's activity history, newest entry date first. Useful as an account-wide feed of what happened. Note what is NOT here: this endpoint takes no since parameter and no date range, unlike the party, opportunity and project listers, so an incremental sync of history means walking pages from the top and stopping at a known id.
Capsule: List Entries on Record
Read the history on one party, opportunity or project: notes, emails and the record of completed tasks, newest first. The type field on each row tells them apart and they are NOT the same shape. A note has content. An email also has subject and a participants array carrying FROM, TO, CC and BCC addresses, and it attaches to a parties array rather than a single party. A task row is the trace a completed task left behind. perPage is capped at 50 on this endpoint, not the usual 100.
Capsule: List Goal Periods
List the periods one goal is broken into, each with its target and its current value. This is where actual progress lives: the goal itself carries the target, and the periods carry what has been achieved. Note that a period's currentValue describes ONE period, so adding periods together across a goal is only meaningful for count and sum goal types and never for the targets.
Capsule: List Goals
List the goals on the account. A goal is a target assigned to a user, measured against opportunities created, won or moved to a milestone, and broken into periods by its frequency. status is read only and is one of UPCOMING, ACTIVE, COMPLETED or MISSED. Goals are a paid-plan feature and the free plan has none.
Capsule: List Lost Reasons
List the reasons an opportunity can be marked lost for. Capsule seeds every account with a set such as Price too high, Competition and Became Stale. The endpoint takes no parameters at all: no paging, no filter. This is the lister behind the lost reason picker on the opportunity nodes.
Capsule: List Milestones
List every milestone on the account across all pipelines. Each row carries the pipeline it belongs to, its win probability and its daysUntilStale threshold. This is the lister behind the milestone picker on the opportunity nodes, where the options are grouped by pipeline name.
Capsule: List Milestones for Pipeline
List the milestones belonging to one pipeline, which is the ordered set of steps an opportunity in that pipeline moves through.
Capsule: List Opportunities
List the opportunities on the account, which is Capsule's word for a potential sale: a bid, a deal or a proposal. Every opportunity has a main party, and that party may be a person or an organisation, so data.opportunities[].party.name is filled for company deals and empty for individuals. Pass since to fetch only what changed. Tags and custom field values need embed.
Capsule: List Opportunities for Party
List every opportunity attached to one party. Covers deals where the party is the MAIN contact; a party added as an additional contact does not show up here, which is a real gap when a deal spans several stakeholders. There is no since parameter on this variant.
Capsule: List Parties
List the people AND organisations on the Capsule account. Both kinds come back interleaved in one parties array, told apart by the type field: a person carries firstName, lastName, title and jobTitle, an organisation carries name, and neither carries the other. Wire a template to the wrong one and it silently produces nothing for half the records. Pass since to fetch only what changed, which is what Capsule recommends instead of re-reading the account. Tags and custom field values are NOT included unless embed asks for them. This is also the connector's auth probe: an invalid token answers 401 here.
Capsule: List People at Organisation
List the people linked to one organisation as employees. The id must be an ORGANISATION party; pointing it at a person returns nothing useful, since Capsule models the link in one direction only. Every row here is a person, which makes this the one party-returning read whose payload is not polymorphic.
Capsule: List Pipelines
List the sales pipelines on the account. A pipeline is an ordered set of milestones an opportunity moves through. Every account has at least one and the free plan is capped at exactly one. Archived pipelines are hidden unless include_deleted asks for them.
Capsule: List Project Boards
List the project boards on the account. A board is the project-side equivalent of a sales pipeline: a visual process made of stages that a project moves through from planning to completion. An account may hold at most 30 active boards, and the free plan has none at all.
Capsule: List Project Stages
List every project stage on the account across all boards. Each row carries the board it belongs to and its displayOrder within that board. This is the lister behind the stage picker on the project nodes, where the options are grouped by board name.
Capsule: List Projects
List projects, which is Capsule's word for work tracked after the sale: onboarding, delivery, a support case, an event. The response key is kases and the path is /kases because Capsule renamed Cases to Projects in the product and deliberately did not rename the API. Every project has a main party and an optional link back to the opportunity it came from. Pass since to fetch only what changed.
Capsule: List Projects for Opportunity
List the projects created to deliver an opportunity, which is the won-deal-to-delivery link. The path says kases because Capsule renamed Cases to Projects in the product and left the API alone, and the response key is kases for the same reason.
Capsule: List Projects for Party
List every project whose MAIN party is this person or organisation. Projects where the party is only an additional contact are not included. No since parameter on this variant.
Capsule: List REST Hooks
List the webhook subscriptions registered on the Capsule account, each with its event, its target URL and whether deliveries are batched. This manages a webhook INSIDE Capsule. It is not a Mattering trigger and it does not make an automation start when something happens in Capsule; the target URL is a receiver you already run. When the connection authenticates as a registered application, Capsule returns only the hooks THAT application subscribed, so an empty list can mean either no hooks or none of yours. Takes no parameters.
Capsule: List Stages for Board
List the stages on one project board, in the order projects move through them. Choose the board first: this is the dependent half of the board and stage pair.
Capsule: List Tag Definitions
List the tags DEFINED on the account for one record type. Tags are per record type in Capsule, so party tags, opportunity tags and project tags are three separate vocabularies and the entity field chooses which one. This lists the vocabulary, not which records carry which tag; to read a record's tags ask for the tags embed on the record itself, and to change them use the tags field on Update Party, Update Opportunity or Update Project.
Capsule: List Task Categories
List the task categories on the account, the coloured labels used to group and report on tasks: Call, Email, Meeting and whatever the account has added. This is the lister behind the category picker on the task nodes. Do not confuse these with activity types, which categorise HISTORY ENTRIES rather than tasks.
Capsule: List Tasks
List tasks on the account. By default Capsule returns only OPEN tasks, which is the single most surprising thing about this endpoint: a workflow looking for completed work gets an empty list and no error. Pass status to widen it. There is no since parameter and no date filter here, so date narrowing means either paging and filtering downstream or using Capsule: Run Filter Query.
Capsule: List Teams
List the teams on the account. Teams own records alongside or instead of individual users, which is how Capsule models shared ownership. Ask for the memberships embed to see who is in each one. Teams are a paid-plan feature starting on Growth, so this returns an empty list on a free or starter account rather than an error. Capsule offers no way to create or edit a team over the API; these two read nodes are the whole surface.
Capsule: List Track Definitions
List the track TEMPLATES on the account, each with the task definitions it will generate. A definition's captureRule says which record type it may be applied to, so filter by type when an automation is about to apply one. This is the lister behind the definition picker on Capsule: Apply Track.
Capsule: List Tracks on Record
List the tracks running on one party, opportunity or project. A track is a track definition that has been APPLIED, so it holds the real dated tasks Capsule generated from the template. Ask for the task embed to see them.
Capsule: List Users
List the users on the Capsule account, with their status, timezone, locale and preferred currency. Each user also has a PARTY record holding their name, email addresses and phone numbers; ask for the party embed to get it. This is the lister behind every owner and assignee picker in the connector, and it takes no paging parameters.
Capsule: Run Filter Query
Run a structured query over parties, opportunities or projects and get back matching records. This is the one node that answers questions the search and list nodes cannot: everyone tagged VIP, every deal added in the last seven days, every project whose custom field has a given value. It is a POST because the query travels in the body, but it READS ONLY and changes nothing. Results come back in exactly the shape the matching list node returns, so parties queries are polymorphic like every other party read.
Capsule: Search Opportunities
Free text search over opportunities, matching what the global search box inside Capsule returns. For a structured query on a named field, a tag or a date range, use Capsule: Run Filter Query with entity set to opportunities.
Capsule: Search Parties
Free text search across people and organisations, returning what the global search box inside Capsule would. Matches names, postcodes and phone numbers loosely, so it is the right tool for does this contact already exist and the wrong one for give me everyone tagged VIP. Results are polymorphic like every other party read.
Capsule: Search Projects
Free text search over projects, returning what the global search box inside Capsule would. For a structured query on a named field, a tag or a date range, use Capsule: Run Filter Query with entity set to kases.
Action nodes 64
Capsule: Add Party to Opportunity
Attach a person or organisation to an opportunity as an additional contact. Both ids go in the URL and there is no request body. Answers 204 with an empty body on success. Reversible with Capsule: Remove Party from Opportunity.
Capsule: Add Party to Project
Attach a person or organisation to a project as an additional contact. Both ids go in the URL and there is no request body. Answers 204 with an empty body.
Capsule: Apply Track
Apply a track definition to a party, opportunity or project, which CREATES all of the definition's tasks at once with dates counted from the track date. This is the closest thing Capsule has to a workflow trigger and it is the highest-leverage write in the connector: one call can schedule an entire onboarding or chase sequence. Set exactly one of party, opportunity or kase, and note these three take a BARE numeric id here rather than an object. A track definition carries a capture rule saying which record types it may be applied to.
Capsule: Archive Pipeline
Archive a pipeline. Capsule spells this as a DELETE but calls it archiving, and it is REVERSIBLE with Capsule: Restore Pipeline, which is why it is not marked destructive. An archived pipeline stops being offered for new opportunities and is hidden from List Pipelines unless include_deleted asks for it.
Capsule: Archive Project Board
Archive a project board. Capsule spells this as a DELETE but calls it archiving, and it is REVERSIBLE with Capsule: Restore Project Board, which is why it is not marked destructive. An archived board stops being offered and drops out of List Project Boards unless status asks for archived or all. It also frees a slot against the 30 active board cap.
Capsule: Create Activity Type
Add a custom activity type. Capsule states this is only possible on a teams edition account, and its plan table shows custom activity types starting on the Growth plan, so a free or starter account gets a plan error rather than an auth error. The icon is chosen from Capsule's fixed set; Capsule: List Activity Type Icons returns it.
Capsule: Create Custom Field
Define a new custom field on a record type. This is account configuration: it creates the field everywhere, it does not set a value anywhere. Setting values is the fields array on Update Party, Update Opportunity or Update Project. The free plan caps the account at 5 custom fields in total.
Capsule: Create Custom Title
Add a custom person title to the account. An account may hold at most 50, and the operation requires the token's user to hold the Administrator role. Note the body root here is personTitle, not title, which the runner handles.
Capsule: Create Goal
Create a goal for one user. Capsule requires a name, a goal type, a frequency, a target value and a date range, and the currency is required for the two SUM goal types and must be null for the COUNT ones. Scope it with at most one of pipeline or milestone, never both. Goals are a paid-plan feature.
Capsule: Create Lost Reason
Add a reason to the account's lost-reason list. Account configuration, not per-deal data: recording that a specific opportunity was lost is done by updating the opportunity. Requires the token's user to hold the Administrator role.
Capsule: Create Milestone
Add a milestone to a pipeline. probability is the default win chance Capsule prefills on opportunities that reach this step, and daysUntilStale is how long an opportunity may sit here before Capsule flags it as stale. Capsule's own create example omits the pipeline entirely, which puts the milestone on the account's default pipeline; name one explicitly whenever the account has more than one. Customizable sales milestones are a paid-plan feature, so this answers a plan error on the free plan.
Capsule: Create Note
Write a note onto a party, an opportunity or a project. The node is named for what the endpoint can actually do: Capsule states that type must be note and that note is currently the only accepted option, so this cannot post an email into the history. Set EXACTLY ONE of party, opportunity or project; Capsule requires exactly one and rejects zero or two. Choosing an activity type is what makes the note show as a Call or a Meeting rather than a plain Note, and some activity types also update the record's lastContactedAt.
Capsule: Create Opportunity
Create an opportunity. Capsule requires three things: a name, a party to attach it to, and a milestone. The milestone is what decides which pipeline the deal lives in, so there is no separate pipeline field. An owner or a team is also required in practice; leaving both empty makes the API token's own user the owner, which for a connector is a shared service identity. Returns the created opportunity with its new id.
Capsule: Create Organisation
Create an ORGANISATION. This is POST /parties with type pinned to organisation, so name is the only identity field and none of the person fields appear. Use Capsule: Create Person for an individual. name is required by Capsule and a create without it answers 422. Returns the created organisation with its new id.
Capsule: Create Person
Create a PERSON. This is POST /parties with type pinned to person, so the fields on offer are the ones a person actually has. Use Capsule: Create Organisation for a company. Linking to an employer is done through the organisation field, and naming an organisation that does not exist yet CREATES it in the same call, which is convenient and is also how duplicate companies appear. Capsule runs no duplicate check here, so calling this twice with the same email makes two people; search first if the workflow can retry. Returns the created person with its new id.
Capsule: Create Pipeline
Create a sales pipeline. A new pipeline needs milestones before opportunities can use it, so pair this with Capsule: Create Milestone, or use Capsule: Duplicate Pipeline to copy an existing one's milestones. Multiple pipelines are a paid-plan feature: the free and starter plans allow exactly one, so this node answers a plan error there rather than an auth error.
Capsule: Create Project
Create a project. Capsule requires a name and a main party. Setting a stage is what places the project on a board, so there is no separate board field; accounts on the free plan have no boards and therefore no stages to choose. Linking an opportunity records that this delivery came from that deal, which is the natural next step after a win. Returns the created project with its new id.
Capsule: Create Project Board
Create a project board. A new board needs stages before projects can move along it, so pair this with Capsule: Create Stage. Capsule caps an account at 30 active boards and the operation requires the token's user to hold the Administrator role, so a non-admin token answers 403 rather than failing validation.
Capsule: Create Project Stage
Add a stage to a project board. Note the inconsistency worth knowing about: board is sent here as a BARE NUMERIC ID, not as an object, which is different from how owner, party and milestone are sent elsewhere in this API. Requires the Administrator role. The free plan has no boards, so there is nothing to add a stage to there.
Capsule: Create Tag Definition
Define a new tag for one record type. This adds it to the account's vocabulary; it does not tag anything. Applying it to a record is done through the tags field on the update nodes, which accept a tag by id or by name.
Capsule: Create Task
Create a task, which in Capsule is a reminder of something to do. description is the one line title and is required; detail is the longer body. A task may hang off a party, an opportunity or a project. Set as many of the three as apply; leaving all three empty makes a standalone reminder. Returns the created task with its new id.
Capsule: Create Task Category
Add a task category to the account. Account configuration: it creates the label, it does not categorise any task. Assigning one is the category field on Capsule: Create Task or Capsule: Update Task.
Capsule: Create Track Definition
Create a track template: a named sequence of tasks with day offsets, which can then be applied to records with Capsule: Apply Track. This is account configuration rather than day-to-day data, so it is the kind of node a setup automation runs once rather than one a workflow calls repeatedly.
Capsule: Delete Activity Type
PERMANENTLY remove an activity type from the account. Capsule documents no undelete and does not document what happens to existing history entries carrying the type, which is the reason to be careful: activity reporting is built on these. Answers 204 with an empty body.
Capsule: Delete Custom Field
PERMANENTLY delete a custom field definition AND every value stored in it, across every party, opportunity and project. Capsule documents no undelete. This is the most quietly expensive delete in the connector: the records survive, so nothing looks broken, and a column of data is simply gone. Answers 204, or 202 Accepted when Capsule queues the work, which is a SUCCESS and must not be retried.
Capsule: Delete Custom Title
Delete a custom person title. Capsule REFUSES while any party still uses the title, which makes this the safest delete in the connector: it cannot silently strip data, it just fails until the title is unused. Requires the Administrator role. Answers 204 with an empty body. Capsule documents no way to UPDATE a title, so renaming means delete then create.
Capsule: Delete Entry
PERMANENTLY delete a history entry AND its attachments. Capsule documents no undelete, and the attachments go with it, so this can destroy the only copy of a file. Answers 204 with an empty body, or 202 Accepted when Capsule queues the work, which is a SUCCESS and must not be retried.
Capsule: Delete Goal
PERMANENTLY delete a goal and its periods. Capsule documents no undelete, and the recorded progress against every past period goes with it. Answers 204 with an empty body.
Capsule: Delete Lost Reason
Remove a lost reason from the account. Softer than most deletes here: Capsule states it MAY KEEP the reason for reporting on historical records while refusing to offer it on new or updated opportunities. It is still marked destructive because there is no documented undo and the account loses a reporting category. Answers 204 with an empty body. Requires the token's user to hold the Administrator role.
Capsule: Delete Milestone
PERMANENTLY delete a milestone from its pipeline. Capsule documents no undelete and does not document what happens to opportunities currently sitting at that milestone, which is reason enough to move them first. Answers 204 with an empty body.
Capsule: Delete Opportunity
PERMANENTLY delete an opportunity. Capsule documents no undelete. If the intent is to record a deal that did not happen, update it with a closed date and a lost reason instead, which keeps it in reporting. Answers 204 with an empty body.
Capsule: Delete Party
PERMANENTLY delete a party. Capsule documents no undelete and no trash for parties. Everything hanging off the record goes with it. Answers 204 with an empty body, or 202 Accepted when Capsule queues the deletion for later, which is a SUCCESS and must not be retried. Deleted ids show up afterwards in Capsule: List Deleted Parties.
Capsule: Delete Project
PERMANENTLY delete a project. Capsule documents no undelete. To retire a project while keeping its history, update its status to CLOSED instead. Answers 204 with an empty body.
Capsule: Delete Project Stage
PERMANENTLY remove a stage from the account. Capsule documents no undelete and does not document what happens to projects currently sitting on that stage, which is reason enough to move them first. Answers 204 with an empty body. Requires the Administrator role.
Capsule: Delete Tag Definition
PERMANENTLY delete a tag definition AND remove it from every record carrying it. Capsule documents no undelete, so a tag applied to a thousand contacts takes that segmentation with it. Answers 204, or 202 Accepted when Capsule queues the work, which is a SUCCESS and must not be retried.
Capsule: Delete Task
PERMANENTLY delete a task. Capsule documents no undelete. To record that the work was done, update the task to COMPLETED instead: that keeps it in activity reporting and writes a completed-task entry onto the record's history, which deleting does not. Check hasTrack first, because deleting a track task breaks a designed sequence. Answers 204 with an empty body.
Capsule: Delete Task Category
Remove a task category from the account. The gentlest delete here: Capsule keeps every task and simply leaves them uncategorised. Still marked destructive because the categorisation itself is gone from those tasks with no documented undo. Answers 204 with an empty body.
Capsule: Delete Track
Remove an applied track from its record AND DELETE EVERY TASK IT CREATED. That second half is the reason this is destructive rather than a tidy-up: a track that generated ten tasks takes all ten with it, including any a person has already been working on. Capsule documents no undelete. Answers 204 with an empty body.
Capsule: Delete Track Definition
PERMANENTLY delete a track template. Capsule documents no undelete. Deleting the TEMPLATE is not the same as deleting the tracks applied from it, which are separate records with their own tasks. Answers 204 with an empty body.
Capsule: Duplicate Pipeline
Copy an existing pipeline, milestones included, which is the quick way to stand up a second process that mostly matches the first. No request body. The copy is a new pipeline with new ids; existing opportunities are not moved into it. Subject to the same paid-plan pipeline limit as create.
Capsule: Remove Party from Opportunity
Detach an additional contact from an opportunity. This removes the LINK only; neither the party nor the opportunity is deleted, which is why it counts as a reversible write rather than a destructive one. Answers 204 with an empty body.
Capsule: Remove Party from Project
Detach an additional contact from a project. Removes the LINK only; neither record is deleted. Answers 204 with an empty body.
Capsule: Restore Pipeline
Bring an archived pipeline back into use. No request body. Find the id with Capsule: List Pipelines and include_deleted set true, since an archived pipeline is otherwise not listed.
Capsule: Restore Project Board
Bring an archived project board back into use. No request body. Find the id with Capsule: List Project Boards and status set to archived, since the default picker only shows active boards.
Capsule: Subscribe REST Hook
Subscribe a webhook so Capsule POSTs to a URL when an event happens. This manages a webhook INSIDE Capsule. It is not a Mattering trigger and it does not make an automation start when something happens in Capsule; the target URL is a receiver you already run. REQUIRES OAUTH, NOT A PERSONAL ACCESS TOKEN. Capsule states that only registered applications can manage subscriptions and that the caller must be authenticated through the full OAuth flow, and separately that the user must hold the Administrator role. A connection holding a personal access token will not be able to run this node. An account may hold 20 subscriptions at once. Delivery is retried five times over 36 minutes and 5 seconds, after which Capsule marks the hook dead and unsubscribes it, and a target answering 410 Gone is unsubscribed immediately, so an endpoint that goes down long enough disappears without further warning. Reversible with Capsule: Unsubscribe REST Hook.
Capsule: Unsubscribe REST Hook
Remove a webhook subscription, stopping deliveries immediately. This manages a webhook INSIDE Capsule. It is not a Mattering trigger and it does not make an automation start when something happens in Capsule; the target URL is a receiver you already run. Reversible in the sense that Capsule: Subscribe REST Hook can recreate it, which is why it is not marked destructive; no Capsule data is deleted, only the subscription. REQUIRES OAUTH, NOT A PERSONAL ACCESS TOKEN. Capsule states that only registered applications can manage subscriptions and that the caller must be authenticated through the full OAuth flow, and separately that the user must hold the Administrator role. A connection holding a personal access token will not be able to run this node. Capsule further requires the SAME registered application that subscribed the hook. Answers 204 with an empty body.
Capsule: Update Activity Type
Rename an activity type, change its icon, or change whether it moves lastContactedAt. Anything not sent stays as it is.
Capsule: Update Custom Field
Partially update a custom field definition. Worth care with options on a list field: dropping a value that records already hold changes what those records mean, and Capsule does not warn about it here.
Capsule: Update Entry
Edit the content of a note or an email in the history. Capsule restricts this endpoint to entries of type email or note, so it cannot rewrite the task rows. Only content and attachments are editable; the record the entry sits on, its activity type and its entry date are not. Removing the last attachment from an entry with no content is a validation error, so delete the entry instead.
Capsule: Update Goal
Partially update a goal. Four things CANNOT be changed and are therefore not offered here: the assignee, the goal type, the pipeline and the milestone. Capsule states this outright, so a workflow that needs to move a goal to another user has to delete it and create a new one.
Capsule: Update Lost Reason
Rename a lost reason or change whether it counts toward the conversion rate. Anything not sent stays as it is. Requires the token's user to hold the Administrator role.
Capsule: Update Milestone
Partially update a milestone. Changing probability affects what Capsule prefills on opportunities reaching this step from now on, not the probability already stored on existing deals.
Capsule: Update Opportunity
Partially update an opportunity: anything not sent stays as it is. Moving the deal along the pipeline means setting a new milestone, which is also what fires Capsule's own opportunity/moved webhook. Marking it lost means setting closedOn and a lost reason; the lost reason on its own is only a reporting label and closes nothing. An owner or a team is required on an opportunity, so do not clear both.
Capsule: Update Party
Partially update a party. One node covers both kinds because Capsule has one endpoint and no type check: fields you do not send stay unchanged. Send only the ones that belong to the kind the id already is. Person fields: first name, last name, title, job title, organisation. Organisation field: name. Everything else applies to both. The collections follow Capsule's three-way convention, so an entry with no id adds, an entry with an id edits, and an entry carrying _delete true removes. This node cannot change a person into an organisation.
Capsule: Update Pipeline
Rename a pipeline or change its description. Its milestones are edited separately with the milestone nodes.
Capsule: Update Project
Partially update a project: anything not sent stays as it is. Moving it to a new stage is what fires Capsule's own kase/moved webhook, and setting status to CLOSED fires kase/closed and makes Capsule stamp the read only closedOn date. An owner or a team is required, so do not clear both.
Capsule: Update Project Board
Rename a project board or change its description. Anything not sent stays as it is. Requires the Administrator role.
Capsule: Update Project Stage
Rename a project stage, change its description, or move it in the board's sequence with displayOrder. Capsule documents no way to move a stage to a DIFFERENT board here. Requires the Administrator role.
Capsule: Update Tag Definition
Rename a tag or change its description, account wide. Turning a DataTag back into a plain tag has an order of operations: Capsule requires every custom field definition linked to the tag to be deleted FIRST, and only then accepts dataTag false.
Capsule: Update Task
Partially update a task: anything not sent stays as it is. Setting status to COMPLETED is how an automation ticks a task off, and it is what fires Capsule's own task/completed webhook. Completing a repeating task also makes Capsule create the next occurrence, readable through the nextTask embed.
Capsule: Update Task Category
Rename a task category or change its colour. Anything not sent stays as it is, and every task already carrying the category picks up the change.
Capsule: Update Track
Rename an applied track or change its anchor date. Capsule allows only these two attributes here; the track's tasks, its definition and the record it runs on cannot be changed. Whether moving the anchor date reschedules the already-generated tasks is not documented, so verify against a real account before relying on it.
Capsule: Update Track Definition
Partially update a track template. Editing task_definitions uses Capsule's three-way convention, so a step with no id is added, a step with an id is changed, and a step carrying _delete true is removed from the template. Changing a template affects tracks applied AFTERWARDS; tracks already running were expanded into real tasks at apply time and do not change.
Capsule: Update User Preferences
Update a user's preferences: locale, currency, timezone, username, task reminder emails and the click behaviour for emails and phone numbers. THIS NODE NEEDS THE user_preference SCOPE. Capsule states it plainly, and the connector's ordinary read write token does not carry it, so a 403 here is the expected outcome rather than a broken connection. The user's name and contact details are not editable here; they live on the linked party record and are changed with Capsule: Update Party.
Connecting Capsule takes one credential
Any Capsule user can generate a personal access token from My Preferences then API Authentication Tokens. Capsule names no plan and no role requirement for it, and the token has no documented expiry, which is why this connector asks for a bearer token rather than running an OAuth dance. Two operations need more than a personal access token can offer and both say so on the node rather than failing mysteriously. Capsule: Update User Preferences requires the user_preference scope, which a personal access token does not document, so a 403 there is the expected answer rather than a defect. And Capsule: Subscribe REST Hook and Capsule: Unsubscribe REST Hook require a registered application authenticated through the full OAuth flow, plus an Administrator role, so a personal access token can list an account's hooks but cannot create one. Several configuration writes, including boards, stages, lost reasons and custom titles, also require the token's user to hold the Administrator role. If you paste an OAuth access token instead, remember Capsule issues those for seven days and this connector does not refresh them for you.
Decide which Capsule user the automations should act as. Every node runs as the holder of the token and inherits their access, and unattended workflows keep running on it, so a user the business controls beats an individual's personal login.
Sign in to Capsule as that user, open My Preferences then API Authentication Tokens, and generate a token. Copy it once and treat it as a password.
In Mattering Automations open Connectors, click Add Connector and choose Capsule CRM, then create a new credential and paste the token as the bearer token. It is stored encrypted and never appears in workflow logs.
Click Test Connection. Mattering calls Capsule's current user endpoint, which is the cheapest authenticated call on the API and cannot be confused by an empty account. A 401 means the token is wrong, revoked or mistyped. A 403 is a different finding: the token is valid and its scope is too narrow for that call.
All 131 Capsule nodes appear in the canvas palette. Run Capsule: Get Current User first, then Capsule: List Parties, which returns people and organisations interleaved with a type field on each row telling you which is which.
If you are on the free plan, expect some pickers to be empty for plan reasons rather than connection reasons. Capsule: List Teams returns nothing and the board and stage pickers have nothing to show, because the free plan includes zero teams and zero project boards. That is a plan boundary, not a broken credential.
Common uses for the Capsule MCP
Keep another system in step without exhausting the rate limit
This is what Capsule's API is best at and the connector is built around it. Capsule: List Parties, Capsule: List Opportunities and Capsule: List Projects each take a since date and return only what changed after it, and Capsule: List Deleted Parties, Capsule: List Deleted Opportunities and Capsule: List Deleted Projects return the ids that went away, which is the half most syncs forget and then quietly keep stale rows forever. A scheduled workflow that walks the changes and then the deletions keeps a Mattering database, a warehouse or another app honest on a handful of requests instead of a full re-read. Two things to build in: Capsule documents no sort order on those listers and pages by number rather than by cursor, so overlap your windows slightly and treat rows as at-least-once rather than exactly-once, and remember that tags and custom field values are omitted from every record unless the node's embed asks for them.
Intake that files a person and an organisation correctly
A form submission, an inbound email or an enrichment step can open the record properly the first time. Capsule: Create Organisation adds the company and Capsule: Create Person adds the individual with their job title and employer, which is two nodes rather than one because Capsule genuinely stores two different shapes. Capsule: Search Parties first is the cheap way to avoid duplicates, and Capsule: Get Multiple Parties fetches up to ten ids in one request when a loop would otherwise spend ten of the account's hourly budget. Capsule: Create Note then writes what the form said onto the record, so the history explains where the contact came from without anybody retyping it, and Capsule: Create Task lays down the follow up.
A deal desk that moves opportunities rather than just reporting on them
Capsule: Create Opportunity needs three things, a name, a party and a milestone, and the milestone is what decides which pipeline the deal lands in. Capsule: Update Opportunity is how a workflow moves it along, because setting a new milestone is the move, and how it records a close, a value or a lost reason from Capsule: List Lost Reasons. Capsule: List Opportunities for Party answers what else is open with this customer before anybody sends a quote, and Capsule: Add Party to Opportunity attaches the other stakeholders on a multi contact deal, which sit alongside the main party rather than replacing it. Read Capsule: List Milestones for Pipeline once and you have the ordered steps and the win probability Capsule prefills at each one.
Turn a won deal into delivery in one call
Capsule: Apply Track is the highest leverage single node in the connector. A track definition is a named sequence of tasks with day offsets, and applying one creates the whole sequence at once with real dates counted from an anchor you pass, so an onboarding, a chase sequence or a renewal run becomes one node instead of a dozen create-task steps that drift out of sync with each other. Capsule: List Track Definitions supplies the template ids, and each definition's capture rule says which record types it may be applied to. Pair it with Capsule: Create Project to open the delivery record and Capsule: Update Project to move it along its board, and Capsule: List Tracks on Record to see what is already running before you start another one.
Ask the structured questions the search box cannot
Capsule: Run Filter Query is the node for questions with conditions in them: every organisation tagged VIP with no activity in ninety days, every opportunity added in the last seven days, every project on a given stage. It runs a structured query over parties, opportunities or projects and returns matching records, which is a different tool from Capsule: Search Parties, Capsule: Search Opportunities and Capsule: Search Projects, and those are free text and match what the global search box inside Capsule would return. This is the natural node to hand an assistant for reporting work, because it answers in records rather than in guesses, and it is a read, so it cannot change anything while it does it.
Keep the account configuration under control
Most CRMs rot at the edges rather than in the middle. Capsule: List Custom Fields returns the definitions for a record type, which is the schema rather than the values, so a workflow can audit what has accumulated before somebody adds a fifty first field nobody fills in. Capsule: List Tag Definitions does the same for tags, per record type, since party tags, opportunity tags and project tags are separate vocabularies. Capsule: List Activity Types, Capsule: List Task Categories and Capsule: List Custom Titles cover the rest. Capsule: List REST Hooks is worth a scheduled read on its own: an account holds at most twenty subscriptions and Capsule marks a hook dead and unsubscribes it after five failed delivery attempts, so an inventory catches a webhook that stopped working weeks ago.
Example: A won deal that opens delivery, schedules the work and tells the team
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule runs every fifteen minutes. This connector has no trigger nodes, so Capsule workflows run on a schedule or start from a trigger elsewhere in the platform, and the REST Hook nodes manage Capsule's own webhooks rather than starting anything here.
Capsule: List Opportunities reads what changed since the last run using the since parameter, so the step costs one request rather than a walk over the whole pipeline, and a condition keeps only deals that have closed as won.
Capsule: Get Party fetches the customer behind the deal. The node's output tells you whether it is a person or an organisation from its type field, which is what decides whether the next steps address a named individual or a company.
Capsule: Create Project opens the delivery record against that party, with a stage that places it on the right board. Stages belong to boards, so the stage is the board assignment, not a separate field.
Capsule: Apply Track applies the onboarding track definition to the new project, which creates its whole task sequence in one call with dates counted from the close date rather than from today.
Capsule: Create Note writes the agreed scope and the deal value onto the project so the delivery team reads it where they already look, and a Mattering Productivity task is opened for the account manager with a link back into Capsule built from Capsule: Get Account Site.
Capsule MCP questions, answered
Does Capsule publish its own MCP server, and why use this connector instead?
Yes, Capsule does, and it is worth knowing about before you choose. There are three vendor artefacts. Capsule announced a local MCP server in its developer changelog on 15 April 2026, available as a private beta, running as a Docker container on your own machine and giving MCP-compatible tools read-only access to parties, opportunities, tasks and projects. Its source is public at github.com/zestia/capsule-mcp-scala, Zestia Ltd being the company Capsule is a service of. And Capsule ships a hosted connector published in Claude's connector directory, installed from Customize then Connectors with your ordinary Capsule login. If you want to ask questions about your CRM in a chat window, that hosted connector is a good answer and it authenticates as you, so it sees exactly what you see. Two things it does not do. Capsule's documentation states that write access is currently limited to updating Custom Fields, and its support page adds that Claude cannot rename a record, reassign its owner or touch any other core field, so it cannot create a contact, log a note, open an opportunity or complete a task. This connector has 64 action nodes that do all of those. And Capsule lists its hosted connector as available on Growth, Advanced and Ultimate, while Capsule's API is included on every plan including Free, so this connector runs on any account. Underneath that is the difference that usually decides it: a vendor MCP server is a chat surface, and these nodes are also canvas steps that run on a schedule with nobody present and chain with every other connector in one workflow.
What can this connector actually do in Capsule?
131 nodes, 67 that read and 64 that act, covering 130 of the 132 operations Capsule documents. Reads cover parties, employees at an organisation, opportunities and the projects delivering them, projects, tasks, history entries on a record and across the account, tracks running on a record, pipelines and their milestones, boards and their stages, lost reasons, tag definitions, custom field definitions, activity types and their icons, task categories, custom titles, teams, users, goals and their periods, countries, currencies, the account site, REST hook subscriptions, free text search across parties, opportunities and projects, and a structured filter query. Writes cover creating and updating people, organisations, opportunities, projects, tasks, notes and tracks, attaching and detaching additional parties, applying a track, archiving and restoring pipelines and boards, duplicating a pipeline, subscribing and unsubscribing REST hooks, and creating and updating the account configuration behind all of it. Sixteen nodes are deletes and every one is flagged destructive. Two things are deliberately not here: uploading a file as raw bytes, and downloading an attachment's contents, because the response is the file itself rather than JSON. Notes can still carry an attachment whose upload token came from somewhere else. The node count runs one ahead of the operation count because Capsule's single party create endpoint is split into a person node and an organisation node.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Capsule through them. Matter, the assistant built into the platform, uses the same nodes natively. Because the same nodes are canvas steps, a workflow an assistant helps you design can then run on a schedule with nobody present. A sensible split with a CRM is to hand an assistant the 67 read nodes freely and put the writes, particularly the 16 deletes, behind a condition or a human approval step. Nothing in Capsule has an undelete.
Do I need a paid Capsule plan?
No. Capsule's plan comparison table lists API Access with a tick in all five columns, Free, Starter, Growth, Advanced and Ultimate, so a free account can generate a token and connect. What the free plan does constrain is what those nodes then find, and that is worth knowing because the failure looks like a broken connector and is not one. A free account is capped at 250 contacts and 5 custom fields, includes 1 sales pipeline, 0 project boards, 0 teams and 0 email templates, and does not include goals, customizable sales milestones or custom activity types. So on Free, the party, opportunity, project, task, history, track, tag, category, lost reason, custom title, user and reference data nodes all work, while creating a board or a stage, creating a second pipeline, creating a goal, creating a custom activity type or adding a sixth custom field comes back as a plan error from Capsule rather than an authentication error. Teams and project boards both start above Free, teams on Growth and boards on Starter, so an empty team list on a small account is a plan answer rather than a fault.
What are Capsule's rate limits, and how should a workflow stay inside them?
Capsule documents 4,000 requests per hour per user for bearer token authentication. Every successful response carries the limit, the number remaining and the time the window resets, and going over returns 429 with a rate limit reached message until the reset. Capsule's own advice is a one second delay between requests, and, for keeping a local copy up to date, the since query parameter on the party, opportunity and project listers plus the deleted endpoints instead of full re-reads. This connector is built around that advice rather than against it: those six nodes are the incremental path, Capsule: Get Multiple Parties, Capsule: Get Multiple Opportunities, Capsule: Get Multiple Projects and Capsule: Get Multiple Pipelines each fetch up to ten records in one request where a loop would spend ten, and paging is by page number with a maximum of 100 records per page, so each node is one request and an unbounded walk cannot hide inside a single canvas step.
Can this start an automation when something changes in Capsule?
Not directly, and the REST Hook nodes are the thing most likely to give the wrong impression, so here is the distinction. Capsule has a webhook system it calls REST Hooks, which posts to a URL you already run when a party, project, opportunity, task or user changes. The four nodes here manage those subscriptions inside Capsule: list them, read one, subscribe and unsubscribe. They are account configuration, exactly like a pipeline or a tag definition, and none of them makes a Mattering automation start. Two of Capsule's own limits apply as well: an account may hold 20 subscriptions at once, hooks must be managed by account administrators, and only a registered application authenticated through the full OAuth flow can subscribe or unsubscribe one, so a personal access token can list hooks but not create them. Until a Mattering trigger for Capsule exists, Capsule workflows run on a schedule, which the since parameter makes cheap, or start from a trigger elsewhere in the platform such as a form submission or an inbound email.
Why is the contact field free text rather than a picker?
Because a picker would be worse than a text box here, and that is a deliberate call rather than an unfinished one. Capsule's party is polymorphic: one collection holding both people and organisations, and the two kinds have disjoint name fields. A person carries firstName and lastName and no name. An organisation carries name and neither of the other two. A picker in this platform reads one label path, so sourcing party labels from name would render every person in the account as a bare numeric id, and sourcing them from lastName would do the same to every organisation. Either way about half the list would show as numbers, which is exactly the failure a picker exists to prevent. So party id fields take an id, and the descriptions point at Capsule: Search Parties and Capsule: List Parties to find it. Everywhere the vendor's data model does allow one clean label, the pickers are there: 88 fields across 52 nodes carry one, with milestones grouped under their pipeline, stages under their board, and tag and custom field pickers narrowing to whichever record type the node is pointed at.
What happens when a workflow deletes something in Capsule?
It is gone. Capsule documents no undelete for any resource and no trash state, which is why all 16 delete nodes are flagged destructive and why several name a reversible alternative in their own description: a task can be completed rather than deleted, a project can be closed rather than deleted, and an opportunity that did not happen can be updated with a lost reason. Three are worth calling out individually. Capsule: Delete Track removes an applied track and deletes every task it created, so it is not a tidy up. Capsule: Delete Custom Field deletes the definition and every value stored in it across every record. Capsule: Delete Custom Title is the safest one in the connector, because Capsule refuses it while any party still uses the title. Two resources have a genuine softer path and get their own nodes rather than a flag: pipelines and boards archive and restore, through Capsule: Archive Pipeline with Capsule: Restore Pipeline and Capsule: Archive Project Board with Capsule: Restore Project Board. One detail that trips workflows up: Capsule may answer a delete with 202 Accepted rather than 204 when it queues the work, and that is a success, so a workflow that treats it as a failure will retry a delete that already happened.
Put Capsule to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Capsule is a product of its respective owner; Mattering is an independent platform.