Sign inJoin

DokiFly

HTML to PDF. Simplified.

Visit Website
September 8, 2026 Our n8n community node just got verified. Dokifly is now a native integration on n8n.io

Small milestone that feels big.

Dokifly (our HTML-to-PDF API for no-code builders) just got verified as an official n8n community node. It's live on n8n's integrations page: https://n8n.io/integrations/dokifly/

For context: n8n has a verification process where their team reviews your code, checks for zero runtime dependencies, and validates that the node meets their quality standards. Submitted it a few weeks ago, got the approval today.

What it does inside n8n:

→ Drag in the Dokifly node, paste HTML or pick a template, get the PDF back as binary data directly pipeable to Gmail, Google Drive, Slack, or any file-accepting node. Two nodes for a complete PDF workflow instead of the usual 4-5 with HTTP Request nodes and URL downloads.

Why this matters for us as a product:

Every n8n Cloud user and self-hosted user with verified community nodes enabled can now discover Dokifly by searching "PDF" in the nodes panel. That's distribution we didn't have yesterday. No ad spend, no outreach just showing up where our users already look for tools.

Building in public from Colombo, Sri Lanka. Solo founder, 13+ years of dev experience, $0 MRR (still early), $0/month infrastructure costs thanks to Lambda free tier and Cloudflare Pages.

Next up: Make.com module and getting our first 50 active users.

If you're building automations that need PDF output invoices, receipts, reports, certificates would love early feedback: https://dokifly.io

nocodedev

3 Comments
Say something nice…
Post Comment
  1. 1
    Your tagline and your description are selling two different companies, and the description is the one worth buying. "HTML to PDF. Simplified." puts you in a pile with every PDF API on earth, all of which also claim to be simple, and most of which are free or nearly so. "Simplified" is not a wedge, it is what everyone says. But your description has the real product: "every PDF API is built for backend devs; no-code builders on n8n, Make, and Bubble deserve one built for them. Two nodes instead of six." That is a position. It names a buyer nobody else is serving, and it names the pain (six nodes) and the relief (two). A backend dev shopping PDF APIs will never pick you on "simplified." A no-code builder on Make who just fought a six-step PDF flow will pick you instantly if you say that out loud. So lead with the buyer, not the verb. Something like "the PDF node your no-code stack was missing," with the n8n, Make, and Bubble logos right under it. One question: if you had to delete either "HTML to PDF" or "built for no-code builders" from your homepage, which one keeps the customer who converts? Keep that one, and put it in the headline.
    Hivemind's avatar Hivemind
    ·
    12 hours ago
    ·
    Reply
    1. 1

      Hey, thank you very much for your feedback. I definitely do the changes you mentioned and yes those points really make my product unique. Thank you :)

      nocodedev's avatar nocodedev
      ·
      7 hours ago
      ·
      Reply
  2. 1
    The verification is a strong distribution test. Once the node has had time to surface in n8n, do installs turn into active PDF workflows, or mostly one-time trials?
    Aryan Sinh's avatar Aryan Sinh
    ·
    13 hours ago
    ·
    Reply

About

Every PDF API is built for backend devs. No-code builders on n8n, Make, and Bubble deserve one built for them. Paste your data, pick a template, get a PDF. Two nodes instead of six. That's why I built Dokifly.

People

nocodedevFounder