CONNECTED WORKFLOW
Send faxes by email
Send a fax from an email account you authorize, keeping number ownership, file handling, status, and failure notifications intact.
CONNECTION STEPS
Connect, verify, recover, and remove.
Send faxes by email should remove a specific manual step without hiding destination review or the final fax status.
- 01Authorize
Use the intended account and only the permissions the workflow needs.
- 02Verify
Send a sample and confirm the resulting Faxoryn record.
- 03Recover
Know how to reconnect and what to use if the connection is unavailable.
- 04Remove
Revoke access when the member, vendor, or workflow ends.
CONNECTION BOUNDARY
The connection moves input or alerts; Faxoryn keeps the fax record.
Authorize the intended account with only the permissions the workflow needs. Use a sample file to check page preview, destination review, and the resulting fax record.
Know how your team reconnects, falls back to local upload, and revokes access when ownership changes. A file in another service, a sent email, or a channel notification is not proof of fax delivery; check the final status in Faxoryn.
ADDRESSING MODEL
Turn the destination address into a complete fax number
When your message arrives, Faxoryn reads the sender and destination addresses, turns each destination into a standard fax number, and records invalid destinations as failed fax activity.
The final email domain must be confirmed by the operating company before launch. Follow the address format shown by your connected account rather than an older branded domain.
ACCOUNT REQUIREMENTS
Send from the account email with an active default number
The sender address must match a registered user. The account must have an active default fax number, because that number is what appears as the sender and authorizes the fax being sent.
Team number access and suspicious-operation checks still apply. Email does not bypass plan, ownership, recipient, or security controls.
DOCUMENT HANDLING
Use attachments or a meaningful message body
Supported attachments are saved to your account and added to the fax. A meaningful message body can also be kept as part of the fax.
A message with neither usable attachments nor meaningful body content is rejected and triggers the corresponding failure notification.
- 01Compose from the email registered to the Faxoryn account.
- 02Address the message using the current account's fax-email format.
- 03Attach the intended documents and remove unrelated signatures or content.
- 04Send, then verify the resulting fax record and final status in Faxoryn.
DELIVERY REVIEW
Use email as an entry point, not the final record
Accepted email content goes through the same fax service as other outbound work. Final delivery or failure is recorded in the Faxoryn fax record.
When a message fails, review sender identity, default number, destination format, attachments, account allowance, and the failure notification before resending.
RECEIVE THROUGH EMAIL
Treat received-fax email as a configured notification path
Receiving requires an active eligible fax number. The carrier and Faxoryn create the inbound record first; configured email recipients can then receive an alert and, where enabled, a document attachment.
The account Inbox remains the main received record with its number, timestamps, sender context, and saved document. Forwarded messages and local email rules can delay, duplicate, filter, or expose copies, so they must not replace your controlled intake process.
- 01Confirm the active fax number and its responsible account or team.
- 02Configure only approved notification recipients and attachment behavior.
- 03Receive a sample fax and compare the email with the Inbox record.
- 04Define who follows unread, filtered, duplicate, or incorrectly routed items.
CLIENT AND FAILURE BOUNDARIES
Use any compatible client without changing the account contract
Gmail, Outlook, Yahoo Mail, and other clients can participate only through the current authorized email format and notification settings. The email brand does not change sender identity, default-number, file, page, destination, plan, or security requirements.
Separate a rejection before the fax is created from a later failure after sending. An unknown sender, missing default number, invalid destination address, empty content, unsupported attachment, missing allowance, or security check can stop the email path before the fax is sent.
COMMON QUESTIONS
Details to check before you continue.
Which email address can submit a fax?
The source address must match the email on a registered Faxoryn account that can use an active default fax number.
Can an email contain only a message body?
A meaningful supported message body can become part of the fax, but an email with neither usable attachments nor meaningful body is rejected.
Where is the fax destination specified?
The current fax-by-email address format includes the destination. The operating company must publish its final domain before launch.
How is email-to-fax delivery confirmed?
The accepted email creates a normal Faxoryn fax record. Use that record's final state; email notifications are secondary alerts.