What it does
TATER uses your organization's HumbleFax account as the fax carrier and gives people a TATER-native way to work with it:
- Receive. Every inbound fax is stored in TATER with its PDF. It appears in the Fax Inbox of each person who has access to that line and in Ops → Fax Numbers → All Faxes.
- Route. A line can open an Ops ticket for each fax, with the PDF attached, and can email the people who have access to it.
- Send. People with access to a line can send a fax from it, from My TATER or from Ops.
- Control access in TATER. Who can see or send from a line is set in TATER. It does not depend on who has a seat in HumbleFax.
Nothing here changes your HumbleFax account. Faxes still travel on HumbleFax's numbers and appear in its portal too.
Before you begin
- A HumbleFax account with API access, and its API access key and secret key.
- An OrgAdmin (or higher) role in the TATER organization, to connect HumbleFax and to set up lines.
1. Connect HumbleFax
- Open TATER Manage → Connections → Integrations (or TATER Security → Settings → Integrations) and choose HumbleFax.
- Enter the API Access Key and API Secret Key and save. TATER encrypts them and never shows them again.
- Choose Test connection. A successful test also registers TATER's webhook with HumbleFax for you, so incoming faxes are pushed to TATER. The result message says so.
There is no webhook URL or shared secret to paste. The webhook address contains a random token generated by TATER, which is what authenticates HumbleFax's notifications, because HumbleFax does not sign them.
If you registered a webhook by hand in the HumbleFax dashboard while testing, you can delete it once TATER's own is in place. Leaving it does no harm.
2. Set up your fax lines
Open Ops → Service Management → Fax Numbers. The table lists every number on your HumbleFax account. An Admin can edit each one:
| Setting | What it does |
|---|---|
| Label | A friendly name shown in place of the bare number, such as "Billing" or "Referrals". |
| Auto-create ticket | When on, each inbound fax opens an Ops ticket with the PDF attached. When off, the fax is still stored and appears in inboxes. |
| Category | The ticket category for those tickets. Defaults to Other. |
| Owning team | The Ops team the ticket is assigned to. |
| TATER access | Who can see this line's faxes in My TATER and send from it. See below. |
| Notify | Email the people with access whenever a fax arrives on this line, whether or not a ticket is created. |
TATER access
Choose TATER access on a line to grant it by email address. This is the only list TATER consults for My TATER visibility, notifications and sending.
- A line that has never been edited falls back to HumbleFax's own assignment, so existing users keep working until you set a list.
- Once you save a list, that list replaces the fallback. Saving an empty list means nobody except admins.
- You can grant someone who has no HumbleFax account at all.
- Admins can see and download every fax. Everyone else sees only the lines they were granted, in the Ops list and in My TATER, and can open only those faxes' PDFs.
3. What happens when a fax arrives
- HumbleFax notifies TATER. TATER fetches the fax's details and its PDF.
- The fax is stored with sender number, receiving line, page count and time received.
- If Auto-create ticket is on, an Ops ticket is opened (channel fax) with the PDF attached, in the line's category and team.
- If Notify is on, everyone with access to the line gets an email, New fax on <number>, linking to their inbox.
If TATER receives the notification but cannot fetch the details or the PDF, the fax is still recorded and the row shows what failed, so a problem is visible rather than silent.
Reading faxes
- My TATER → My Fax Numbers shows the lines you have access to and your Fax Inbox. Choose a fax to download its PDF.
- Ops → Fax Numbers → All Faxes lists faxes across lines, inbound and outbound. Admins see every line; others see only theirs.
Sending a fax
- Choose + Send a fax in My Fax Numbers or in Ops → Fax Numbers.
- Pick the line to send From. Only lines you have access to are listed.
- Enter the To number, 10 or 11 digits (US and Canada).
- Optionally add a recipient name, subject or cover message. Filling in any of them adds a cover sheet.
- Attach the file, up to 20 MB, and send. PDF is the safe choice.
TATER hands the fax to HumbleFax and records it as an outbound fax, keeping a copy of the file you sent. Delivery happens afterwards, so the status shown is what HumbleFax reported at the time of sending. The final result is in HumbleFax. Executable and video files are refused.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| Test connection fails | Re-enter both keys and confirm API access is enabled on the HumbleFax account. |
| A fax arrived in HumbleFax but not in TATER | Run Test connection again to re-register the webhook, then send another test fax. |
| The fax is listed but has no PDF | The row shows the fetch error. The fax is still in HumbleFax; download it there. |
| My Fax Numbers is empty | You have not been granted a line. Ask an admin to add you under Ops → Fax Numbers → TATER access. |
| "You do not have access to send from this number" | Same fix: your email must be on the line's access list. |
| No ticket was created | Check Auto-create ticket on that line. The fax is still in the inbox either way. |
| "HumbleFax is not connected" | The connection has not been saved for this organization. See step 1. |
A note on content
Faxes often carry sensitive material. Stored PDFs sit in your organization's TATER storage and are served through short-lived download links, and access follows the line's list as described above. A ticket created from a fax is visible to whoever can see that ticket's queue, so give a sensitive line a category and team whose queue is restricted accordingly.