A connection holds the provider account or bot configuration. A destination identifies where content is meant to go. A profile brings approved routes and publishing choices together.
Start with one destination
- Open the plugin’s Networks / Connections section and choose a provider.
- Follow that provider’s current credential instructions. Enter secrets only in the protected plugin form.
- Add or discover the intended destination where the current connector supports discovery. Check channel or chat identifiers carefully.
- Review the connector’s capabilities, required rights, and any limitations shown in the plugin.
- Assign a destination to an approved publishing profile, then review a local preview.
Each network has its own rules
Text, media, buttons, replies, edits, and deletion are separate capabilities. A feature supported by one connector may not be available on another. Current source notes include specific limitations for Eitaa inline buttons and Rubika URL navigation.
Keep credentials private
Encryption normally derives from the existing WordPress authentication keys. Protect those keys together with your backups. Do not include tokens, license values, or configuration keys in screenshots or support reports.
Customer connection guides; README current network-capability notes, NETWORK_CAPABILITIES_150.md, EITAA_INLINE_151.md.