Description

n8n-nodes-linkatudo-hub

This n8n community node connects workflows to the Linkatudo Hub public API. It discovers account channels, sends provider-neutral messages, lists WhatsApp templates, reads retained contacts, and checks asynchronous delivery status.

n8n is a workflow automation platform.

Installation

Follow the n8n community node installation guide, then install n8n-nodes-linkatudo-hub.

Operations

Channel

• Get Many: retrieve all non-deleted channels registered for the account.

Message

• Send: submit one or more contents through a selected channel.
• Supported content types: text, file, sticker, location, reaction, interactive, contact, and template.
• JSON Array input accepts one to ten API content objects.
• Guided Form input covers every supported content type for a single content object.
• Optional replies use reply and messageId.
• Optional Idempotency-Key prevents duplicate acceptance when retrying the same request within its active period.

Template

• Get Page: retrieve one page of approved WhatsApp templates.
• Use the opaque nextCursor response value as After Cursor to fetch the next page.
• Templates are available only for supported active WhatsApp channels.

Contact

• Get: retrieve a retained account contact by ID.

Delivery

• Get: retrieve asynchronous message delivery status by the requestId returned from Message > Send.

Credentials

Create a Linkatudo Hub API credential with:

• Base URL: root URL of the Hub installation. Default: https://hub.linkatudo.app.
• Account ID: account associated with the API key.
• API Key: secret account API key sent through the X-Api-Key header.

The credential test lists account channels. A missing, invalid, or account-mismatched key returns an authorization response.

Usage

1. Add Linkatudo Hub to a workflow.
2. Select Channel > Get Many to discover available channel IDs.
3. Select Message > Send.
4. Choose a channel from the list or enter its ID.
5. Enter the provider-specific recipient identifier.
6. Select Guided Form for one content or JSON Array for one to ten contents.
7. Use the returned requestId with Delivery > Get when delivery status is needed.

Recipient formats depend on the selected channel. Examples include an international phone number for WhatsApp, PSID for Facebook Messenger, IGSID for Instagram, or chat ID for Telegram.

Delivery Safety

Message submission is asynchronous and returns HTTP 202 with a requestId. The node does not poll or retry automatically. Supply a UUID as Idempotency-Key when the same request may be retried. The API keeps active idempotency keys for 24 hours after acceptance.

Provider rules still apply. For example, Meta channels can require a retained contact with a recent inbound message, and unsupported content types return an API error.

Resources

• Linkatudo Hub API documentation
• Linkatudo Hub OpenAPI contract
• n8n community nodes documentation

License

MIT