Receive faxes in Gmail

Receive faxes in Gmail is used for email notification and attachment delivery for received faxes. It should not remove the review step or obscure the final delivery state.

Use the least access the connection needs, confirm the supported file and event behavior, and keep a local upload or workspace fallback for carrier outages.

This page covers receive, gmail. Check the relevant account setting or fax record before you continue.

• Confirm the account and permission scope used by Receive faxes in Gmail.
• Review imported files before sending them.
• Keep the Faxoryn activity record as the main delivery record.

Under Profile notifications, configure the registered Gmail address or approved recipients and choose whether received-fax alerts include the attachment.

If an authorization expires or a carrier is unavailable, the workspace should direct the person to reconnect or use another supported input path.

1. 01Authorize the intended Receive faxes in Gmail account or workspace.
2. 02Select the minimum file, channel, or event permissions required.
3. 03Send one sample document through the connection.
4. 04Receive a sample fax, confirm the Gmail notification behavior, and verify that Inbox still contains the main document and its details.

Remove the Receive faxes in Gmail connection when it is no longer required, and revalidate it after ownership, credentials, or workspace policy changes.

Receive faxes in Gmail may hold the original file, sent message, copied PDF, or notification, depending on the configured path. Faxoryn retains the fax record number, formatted destination, fax pages, carrier progress, and final delivered or failed state.

Record the source-system reference when the workflow must be matched later. A copied file or channel message can help a team find the work, but it must not be treated as independent proof that the fax destination received it.

• Confirm where the editable source and approved version are retained.
• Use the Faxoryn record number to investigate delivery and duplicate sending.
• Define whether connected copies are records, notifications, or temporary working files.

Authorization can expire, file permissions can change, an account can be removed, or Receive faxes in Gmail can become temporarily unavailable. Surface that condition before sending whenever possible and do not silently omit a source file or event.

Reconnect only the intended account, then repeat the check with a sample document. For urgent work, use an approved local upload or workspace path and link the resulting record to the same business process without creating duplicate faxes.

Choose approved notification recipients, decide whether attachments may be included, and test message filtering on both desktop and mobile clients. A mailbox rule, spam filter, storage limit, forwarding setting, or revoked account can prevent the alert even when Faxoryn received the fax correctly.

Keep Inbox as the main record of the document and its details. Use the email message for awareness and routing only according to the organization's attachment, retention, and access policy.

• Verify the active fax number and inbound assignment before testing email.
• Confirm subject, sender, recipient list, attachment behavior, and mobile notification.
• Remove former employees and unintended forwarding rules promptly.
• Investigate missing alerts separately from missing inbound faxes.

An attached received fax can be stored in Gmail, synced to phones and computers, included in backups, forwarded, downloaded, or exposed through delegated mailbox access. Approve that data path before enabling attachments for confidential workflows.

When attachment delivery is not appropriate, send a minimal alert and require authorized users to open the workspace record instead.