Documentation

ConverzaFlow channels and credentials

Official messaging onboarding, Meta callbacks, mail, and the rule that secrets stay in .env.

ConverzaFlow product page Open live demo

Rules

Channels — Connect official providers from the product UI.

Channel setup — Verify credentials, then use Inbox.

Secrets in .env or a secret manager — never in VITE_* variables, tickets, or screenshots
Separate development, staging, and production credentials
After changing .env: php artisan optimize:clear and restart workers
Keep .env outside web access

Official messaging

Workspace users do not paste Meta app secrets into the inbox. The deployment owner creates one Meta application and configures META_APP_ID, META_APP_SECRET, redirect URIs, and the Graph webhook (/webhooks/meta/events).

WhatsApp uses Meta Embedded Signup. Instagram and Messenger use Pages messaging permissions. Telegram uses a BotFather token.

Mail

Transactional mail uses SMTP from .env. Production preflight rejects MAIL_MAILER=log and array. Verify SPF, DKIM, and DMARC for the sender domain.

Typical SMTP

MAIL_MAILER=smtp
MAIL_SCHEME=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=587
MAIL_USERNAME=…
MAIL_PASSWORD=…
MAIL_FROM_ADDRESS=support@example.com

Still stuck?

Check the setup guide bundled with your download first — it is specific to the release you own. If that does not resolve it, open support and include your Envato purchase code so we can match the licence.

Go to support