The Titan n8n community node (Documentation Index
Fetch the complete documentation index at: https://docs.usetitan.app/llms.txt
Use this file to discover all available pages before exploring further.
n8n-nodes-titan) integrates the Titan WhatsApp API into your n8n workflows. It covers all major Titan operations across 13 resources and exposes 30 trigger events for real-time workflow automation. Access to the Titan API is gated by your plan and API key — the community node itself is publicly available on npm.
Installation
- n8n community nodes UI
- npm (self-hosted)
In your n8n instance, go to Settings → Community nodes → Install and enter:Restart n8n after installation.
Credentials
After installing the node, add a Titan API credential in n8n:- Go to Credentials → New credential → Titan API.
- Enter your base URL (for example,
https://api.example.com) and your API key (starting withtitan_). - Save. n8n stores the credential securely and uses it in every Titan node in your workflows.
Resources
The node covers 13 resources that map directly to Titan API domains:| Resource | Operations available |
|---|---|
| Sessions | Create, start, stop, restart, get, list, delete |
| Messages | Send (text, image, video, audio, document, poll, location, contact, sticker), react, edit, delete, mark seen, typing indicator |
| Contacts | List, get, check number, get picture, block, unblock |
| Groups | Create, get, leave, delete, update settings, manage participants, invite links |
| Channels | Create, delete, list, get, follow, unfollow, mute, unmute |
| Presence | Get presence, set status, subscribe |
| Profile | Get, set name, set status, set picture |
| Labels | List, create, update, delete, assign to chat |
| Chats | Archive, unarchive, mute, mark read, delete |
| Webhooks | Create, list, get, update, delete |
| Pairing | Request QR code, request pairing code |
| Media | Download, get info, persist to S3 |
| Client tokens | Mint token, get rules, set rules, delete rules |
Trigger node
The Titan Trigger node subscribes to any combination of the 30 Titan event types and starts your workflow when an event arrives. Events are delivered in real time via webhooks. To use it, add a Titan Trigger node, select your credential, choose the session to monitor (or leave blank to receive events from all sessions), and select the event types to subscribe to.Available trigger events
Messages (9 events)
Messages (9 events)
message.received, message.sent, message.ack, message.revoked, message.reaction, message.edited, message.update, message.delete, message.voteSessions (4 events)
Sessions (4 events)
session.status, session.qr, session.connected, session.logged_outGroups (2 events)
Groups (2 events)
group.update, group.participantCalls (4 events)
Calls (4 events)
call.received, call.missed, call.accepted, call.rejectedOther (11 events)
Other (11 events)
presence.update, contact.update, chat.archive, chat.mute, chat.read, chat.clear, chat.delete, labels.update, newsletter.update, blocklist.update, history.syncExample workflows
Incoming message → parse intent → send reply
A Titan Trigger node fires on
message.received. An AI node (OpenAI, Anthropic, or your own) classifies the intent. A Titan Messages node sends the appropriate reply back to the sender.New session connected → send welcome message
A Titan Trigger node fires on
session.connected. A Titan Messages node sends a welcome message to a predefined contact or group to confirm the session is live.Group participant joined → send onboarding message
A Titan Trigger node fires on
group.participant with action add. A Titan Messages node sends a personalized onboarding message to the new participant’s JID.CRM webhook → send WhatsApp notification
An HTTP node or CRM trigger node starts the workflow. A Titan Messages node sends a WhatsApp message using the phone number from the CRM payload.
Access and limits
The community node uses your Titan API key for all operations. Your Titan plan’s rate limits, session limits, and message throughput limits apply normally. n8n’s own execution limits depend on your n8n plan and instance configuration.The
n8n-nodes-titan package is published publicly on npm. Any n8n instance can install it, but the API calls it makes require a valid Titan API key and a Titan plan that covers the operations you use.