Connectors overview
Knot Tools™ groups connectors by category. Each canvas node calls a connector to read or write data, call an API, or apply logic.
🔌 Catalog by category
| Category | Role | Detailed guide |
|---|---|---|
| Dolibarr | CRUD on mapped ERP objects (third parties, invoices, orders, etc.) | Dolibarr connector |
| HTTP | Outbound REST calls, response parsing (Pro Pack) | HTTP and webhooks |
| Outbound messages, attachments, templates | Email connector | |
| AI | Calls to a configured AI provider (OpenAI, Anthropic, local) (Pro Pack) | AI connector |
| Logic | Branching, loops, delays, error handling | Logic connector |
🔌 Picking the right connector
- Data already in Dolibarr → start with the Dolibarr connector (respects multi-entity and user rights).
- External system (CRM, line-of-business API) → HTTP with a dedicated credential.
- Human notification → Email (check your instance SMTP settings).
- Decision or transform without network → Logic.
- Text, summary, or extraction → AI after configuring a provider.
🔌 Shared best practices
- One workflow = one clear business responsibility; avoid huge graphs that are hard to Simulate.
- Reuse encrypted credentials instead of pasting keys into every node.
- Test with dry-run (Simulate) before activating a production trigger.