Understand supported attachment categories

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to use only media types accepted by the module allowlist, including supported image, audio, video, PDF, text and office-document formats.

What this guide helps you do

Use only media types accepted by the module allowlist, including supported image, audio, video, PDF, text and office-document formats. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

1. Go to Admin Area → WhatsApp → Inbox → Open conversation.
2. Find the account, conversation, setting, session or evidence relevant to “Understand supported attachment categories”.
3. Check the displayed value or behaviour against this guide’s code-backed rules.
4. Do not change unrelated account, CRM or connector settings while verifying the result.
5. Verify the expected state in the related Inbox, Connections, customer history, native CRM record or Audit Trail.

Fields and options

Rules and limits

• A send request requires reply permission and either non-empty text or one accepted attachment.
• The server validates MIME type using file content and stores a randomised filename in the protected upload area.
• Opening an unread conversation asks the linked device to send a real read acknowledgement before clearing CRM unread state.
• Use only media types accepted by the module allowlist, including supported image, audio, video, PDF, text and office-document formats.

Check it worked

• The requested action completes without a permission, validation, connector or native CRM error.
• The selected account or conversation shows the expected state without changing another account’s data.
• Where the action creates evidence, confirm the message, native record, verification event, portal history or audit entry is present.

Security, privacy and troubleshooting checks

• Never expose connector tokens, loopback ports, authentication directories or raw customer verification replies.
• Use the supported Connections, Access Control, Settings and Audit Trail pages rather than editing runtime or database records directly.
• If the expected control is missing, verify both native capability and per-account permission before treating it as an installation fault.

Related guides