Explanation
Explanation is for understanding. These pages give background, context, and the reasoning behind how Drum works.
They are not instructions. When you need to complete a job, use a how-to guide. When you need a fact, use reference.
API
- How the Drum API works: Why API requests act as a person, why fields come and go with permissions, and how opportunities, projects and money are represented.
Webhooks
-
How Drum webhooks work: What happens between a change in Drum and a request at your endpoint, and why delivery is at least once, unordered and combined.
-
Webhooks, the API or event triggers?: When to listen for webhooks, when to read the REST API, when to use an event trigger, and why most integrations use webhooks and the API together.
MCP server
-
How AI assistants work with Drum: Why an AI assistant acts as you, why its tools come in toolsets, why it sees only what your role permits, and how it relates to the REST API.
-
Keeping AI access safe: The risks of giving an AI assistant access to Drum, what Drum does about each, and what is left to you.
-
MCP or the REST API?: How Drum’s MCP server and REST API differ, and which to use for an integration, an assistant or an agent.