Weave Code
Interfax Laravel Package
laravel-notification-channels/interfax
Laravel notification channel for sending faxes through InterFAX. Add fax delivery to Laravel notifications so your app can notify users or systems via InterFAX using a simple, consistent channel API.
This package makes it easy to send files as faxes via InterFAX with Laravel notifications
Frequently asked questions about Interfax
- How do I install and configure the InterFAX notification channel in Laravel?
- Install it with composer require laravel-notification-channels/interfax, publish the package config, and add your InterFAX username and password to config/services.php. Then create a notification class whose via() method returns the package's Interfax channel and whose toInterfax() method supplies the fax payload. No service container rewiring is required, so adoption is additive and reversible.
- Which Laravel and PHP versions does laravel-notification-channels/interfax support?
- Version 8.0.0 adds Laravel 13 support and drops Laravel 11, and PHP 8.5 is included in the CI matrix. The CI matrix is not the same as composer.json constraints, so verify the package's actual Laravel and PHP requirements before upgrading, including whether Laravel 12 is still allowed. If you are on Laravel 11 or older, v8 is not installable and you will be pinned to v7.x on an unsupported branch.
- How do I send a fax from a Laravel notification using InterFAX?
- Create a notification and have via() return the package's Interfax channel. Implement toInterfax() to return the payload InterFAX expects, typically a document ID plus the destination fax number. Dispatch the notification with Laravel's Notification facade as usual; the channel handles the API call. Remember that success means InterFAX accepted the request, not that the fax was delivered.
- Do I need to upload a PDF or TIFF before sending a fax with this package?
- Yes. InterFAX requires you to upload a PDF or TIFF document first and then send by referencing the returned document ID. This package is a thin transport channel; it does not render documents or manage a document pipeline. Your application must render the fax artifact and upload it before dispatching the notification.
- Does the package validate or normalize fax numbers?
- No. The channel will not validate or normalize fax numbers for you. You should validate and convert destination numbers to E.164 before dispatch, otherwise InterFAX may reject the send or route it incorrectly. Build this into your notification payload preparation.
- How can I test InterFAX notifications in Laravel without sending real faxes?
- The package does not provide a channel-specific fake() helper, so use Laravel's Notification::fake() to assert that the notification was dispatched. For transport-level tests, stub or mock the InterFAX PHP SDK so no real fax is sent. Keep a small integration test against a sandbox or test account if InterFAX provides one, and assert your payload shape separately.
- Can I track whether a fax was delivered or failed?
- Not directly. Notification dispatch returns success when the InterFAX API accepts the request, not when the fax is transmitted or delivered. There is no built-in delivery-receipt webhook or reconciliation loop. For production, poll InterFAX status endpoints or consume its callbacks and store delivery outcomes in your own system.
- How should I handle InterFAX credentials for multi-tenant Laravel apps?
- InterFAX credentials are account-level username and password values, so the default config assumes one account. For multi-tenant or per-brand sending, you need separate configuration handling and likely separate channel instances or credentials per tenant. Do not rely on a single global config if tenants must send from different InterFAX accounts.
- What are the alternatives to using this package for fax notifications?
- You can call the InterFAX PHP SDK directly if you need more control over document upload, sending, and status checks. For simpler notifications, mail or SMS channels may be a better fit than fax. If you need a Laravel-native channel API, this package is a thin wrapper and alternatives depend on your fax provider and compliance requirements.
- Is this package actively maintained, and what risks should I consider?
- The project has a low evidence base: 1 star and 0 dependents, with a bus factor of 1. However, v8.0.0 was a positive signal because a contributor shipped Laravel 13 support and PHP 8.5 CI promptly. It still wraps the InterFAX PHP SDK, so pin and test SDK constraints, and treat major upgrades as requiring a full regression pass. For regulated fax workflows, vendor and compliance review will usually matter more than the package choice.
Weaver
How can I help you explore Laravel packages today?