Integrations

curl -X POST "https://api.telnyx.com/v2/faxes" \
  -H "Authorization: Bearer txai_example_8k2m4q7p" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "2935264480004671439",
    "from": "+17869848552",
    "to": "+13051234567",
    "media_url": "https://app.nomadfiling.com/storage/faxes/fil_9a2c7b1d.pdf",
    "quality": "high"
  }'

{
  "data": {
    "id": "fax_01hv8s4n2p9x6m",
    "status": "queued",
    "from": "+17869848552",
    "to": "+13051234567",
    "connection_id": "2935264480004671439",
    "quality": "high"
  }
}

Nomadfiling connects payments, filing delivery, document generation, and account data through a small set of third-party services

Most integrations in Nomadfiling support a specific filing workflow: collect payment, generate PDFs, send forms by fax, and track the result.

Use this page to understand what each integration does, where it appears in the product, and what data or actions depend on it.

Stripe payments

Stripe handles one-time checkout for Nomadfiling purchases. It is used for the main filing tiers, Form 7004 extension checkout, receipt URLs, promotion codes, and metadata passed into payment records.

Nomadfiling offers four pricing tiers, ranging from $147 to $497, through Stripe-powered checkout flows.

Stripe workflows in Nomadfiling

• Main filing checkout for product tiers shown on Pricing
• Extension checkout for Form 7004 purchases
• Payment verification after checkout completes
• Receipt URL storage for paid orders
• Promotion code support during checkout

Stripe edge functions

• create-checkout
• create-extension-checkout
• verify-payment

Telnyx fax delivery

Telnyx sends tax form PDFs to IRS fax numbers. When you use Nomadfiling's fax workflow, the app prepares the PDF package, submits it to the Telnyx Fax API, and records the send attempt for later status updates.

This integration powers the product's fax delivery flow described in Fax service.

Fax API configuration

Edge functions

• send-fax sends the fax and writes a record to fax_logs
• telnyx-fax-webhook receives status updates from Telnyx after submission

Success usually looks like a queued or accepted fax record followed by later webhook updates. Nomadfiling uses those webhook events to keep fax status in sync.

AI API compliance and statement generation

Nomadfiling uses an AI API for two focused tasks: checking generated PDFs for likely IRS filing issues and drafting supporting statement text. The AI layer supports review and drafting, not the underlying tax form generation itself.

These features appear in product workflows such as the AI compliance scanner.

Edge functions

• analyze-pdf checks PDFs for filing or formatting issues
• generate-statement drafts IRS supporting statement text

PDF generation and ZIP bundling

Nomadfiling generates filing documents in the browser. After generation, it can bundle multiple PDFs into a ZIP archive for download.

This integration layer is what turns filing data into completed IRS forms, cover sheets, supporting statements, and packaged document sets.

PDF generation

The document generator fills IRS form templates stored under /public/templates/. The generated output includes both core returns and supporting documents.

Supported document generation includes:

• Form 5472
• Form 1120
• Form 1065
• Schedule K-1
• Schedule K-2
• Schedule K-3
• Form 8804
• Form 8805
• Form 1040-NR
• Form 7004
• Fax cover sheets
• Late filing letters
• Supporting statements

ZIP bundling

When a filing includes multiple generated documents, Nomadfiling packages those PDFs into a single ZIP download. This is especially useful for multi-document or multi-party filing flows.

A successful ZIP workflow ends with a browser download containing all generated PDFs together rather than separate file downloads.

UI component libraries

Nomadfiling uses shadcn/ui and Radix UI for application interface components. These libraries are not external workflow integrations in the same sense as payments or fax delivery, but they are part of the platform stack readers often ask about.

The codebase includes 46 generated UI components for common interface patterns such as buttons, dialogs, selects, and tables.

How the integrations fit together

Most user-facing filing flows follow the same sequence: create or update filing data, pay if required, generate documents, then deliver or download the result.

That sequence is why service health can affect different parts of the product in different ways. A payment issue does not stop sign-in, but a storage or fax issue can affect delivery.

Related product areas

Common questions