All resources

Your tools.
Connected.

Send email from your business domain and WhatsApp messages from your business number. Follow the steps below, one connection at a time.

Open Integrations

You can start without an integration. Hemxi email is built in. New email actions use it when no verified business sender is available. WhatsApp always needs a connected Meta account.

01 / EMAIL

Connect your business email

This integration sends through Resend. It does not sign in to a Gmail or Outlook inbox. Use a domain you own, such as mail.your-business.com.

Have these ready

  • A Resend account and a Full Access API key.
  • A business domain and access to its DNS settings.
  • Your sender name and an existing inbox for replies.
  1. Get your Resend API key

    Open Resend API keys, create a key for Hemxi with Full Access, and copy it securely. Hemxi needs domain access to find, register, and verify your sending domain. A sending-only key cannot complete this setup.

  2. Enter your sender details

    In Integrations, select Business email. Enter your domain and paste the key. For “Sender name before @”, enter only bookings, for example. Add your business display name and reply-to address if needed.

    Example sender: Your Studio <bookings@mail.your-business.com>

  3. Connect and add the DNS records

    Select Verify and connect. Hemxi finds your domain in Resend or registers it in that account. If DNS is pending, your connection is saved and the page shows the records to add at your DNS provider.

    Copy each record’s type, name, value, and priority where shown. Use the exact records for this domain. Keep existing mailbox records intact; ask your domain administrator if you are unsure.

  4. Wait for verification

    After adding the records, select Check DNS & connection. DNS updates can take time. Continue when the status is Ready to send. Connecting a domain does not create an inbox; replies need the existing address you supplied.

02 / WHATSAPP

Connect your business number

Hemxi connects to Meta’s WhatsApp Cloud API. Installing the WhatsApp Business mobile app alone does not complete this connection.

Have these ready

  • A Meta business portfolio, app, and WhatsApp Business Account.
  • A business phone number verified and registered for Cloud API.
  • A system user access token with WhatsApp management and messaging permissions.
  1. Set up your WhatsApp account in Meta

    Open Meta for Developers and your app’s WhatsApp setup. Complete the business account and phone onboarding, including verification and Cloud API registration. Follow Meta’s instructions for your number, account eligibility, and any required billing setup.

  2. Copy the two IDs and create your token

    Copy the WhatsApp Business Account ID and Phone number ID for the same account. These are different from your general business ID and the actual phone number.

    In Meta Business Settings, assign the app and WhatsApp assets to a system user. Generate its token with whatsapp_business_management and whatsapp_business_messaging. Check its expiration; a temporary setup token is unsuitable for ongoing automations.

  3. Verify the connection in Hemxi

    Select WhatsApp in Integrations, paste both IDs and your token, then select Verify and connect. Hemxi checks that the verified phone belongs to your account and loads its templates. Credentials are stored encrypted.

  4. Prepare an approved message template

    In WhatsApp Manager, create a template in the business account connected to Hemxi and wait for Meta’s approval. Approval in another business’s account does not make the template available here. Reconnecting the same account does not require a new submission. Hemxi supports numbered body variables such as {{1}} and {{2}}. Start with a body-only template. Named variables, media headers, and dynamic header or button variables are not supported by this builder.

    In your automation, choose from the templates loaded from your connected account. The language and required fields appear automatically. In Integrations → WhatsApp → Templates, use Sync templates after Meta approves a new template. The library loads automatically when you open it. Hemxi checks approval again before sending; paused, rejected, or missing templates cannot be used.

03 / DELIVERY TRACKING

Know when messages arrive

For WhatsApp, open Delivery & webhooks. For business email, expand Delivery tracking. Webhooks let your provider report delivery and failures to Hemxi. Your connection can be saved before tracking is configured.

Business email

  1. Copy your callback URL from Hemxi.
  2. Add that endpoint in Resend Webhooks. Subscribe to sent, delivered, delayed, bounced, complained, and failed email events.
  3. Copy the endpoint’s signing secret, beginning whsec_, into Hemxi and select Save callback verification.
Resend webhook guide

WhatsApp

  1. In Hemxi, enter your Meta App Secret and generate a callback verification token. Copy the token before saving.
  2. Save these in Hemxi before verifying the callback in Meta.
  3. In Meta, use the same callback URL and token, subscribe to the messages field, and subscribe your app to the WhatsApp Business Account.
Meta webhook subscription guide

“Awaiting updates” means the verification credentials were saved. It is not proof of delivery. “Receiving updates” appears after a valid provider callback. Localhost cannot receive these callbacks; your administrator needs a public HTTPS backend.

04 / PUT IT TO WORK

Choose a sender in Automations

  1. Pick your delivery channel

    Open an automation and select its message step. New email steps use your verified Business email when available, otherwise Hemxi email (default). Existing workflows keep their saved sender. Select WhatsApp for a WhatsApp template message.

  2. Complete the message

    For email, add a subject and message. For WhatsApp, select an approved template from your connected account and fill its numbered body values. Record the customer’s WhatsApp opt-in and use a phone number with country code.

  3. Preview, then publish deliberately

    Test flow previews the workflow without sending. Review its recipient and content before publishing. Live messages require the delivery worker to be enabled. A provider acceptance receipt does not yet mean delivery; check delivery history and callbacks.

Disconnecting an account does not delete it at the provider. Existing automations using that account stop sending until you reconnect or edit their channel. Hemxi does not silently switch an explicitly selected business sender or WhatsApp message to another channel.

05 / NEED A HAND?

Common setup questions

My email connection says “DNS verification needed”.

Your credentials are saved, but the domain is not ready. Check the records shown under Domain verification against your DNS provider, allow time for updates, and run Check DNS & connection again. Do not repeatedly create new API keys.

My API key or token was rejected.

Use credentials from the account that owns your domain or WhatsApp number. Resend needs Full Access. Meta needs both WhatsApp permissions and access to the correct assets. Replace expired or revoked credentials using Update connection. Leave the secret field blank only when keeping a saved credential.

WhatsApp says the phone is not in this account.

Copy the WABA ID and Phone number ID from the same Meta account. Do not enter a general business ID or your phone number. Finish phone verification and registration in Meta first.

The account is connected, but messages are not sending.

Confirm the automation uses the intended channel and is published. Check whether the delivery worker is paused. WhatsApp also requires an approved, supported template and customer opt-in. Review delivery history for provider limits, account restrictions, or a rejected message.

I see a server setup or storage message.

Ask the Hemxi administrator to resolve the issue shown under Technical details. Re-entering your provider credentials will not fix server configuration. Share the reference ID with support, never your key or token.

The request timed out or another session changed the connection.

Select Refresh status before retrying. A previous save may have finished. Refreshing loads the latest saved connection and prevents an older form from overwriting it.

Connect your account