hecigo Developer Resources

Everything hecigo publishes for developers and for automated clients, in one place. This page is the index; each entry below is a stable, predictable URL you can bookmark or hard-code.

If you are an AI agent, start with hecigo.com/llms.txt — it names what this site is for and when to reach for us.

Open-source n8n nodes by hecigo

hecigo maintains two n8n community nodes on npm. Both are MIT licensed, both are used outside our own projects, and both take issues.

n8n-nodes-zalo-platform

An n8n community node for the Zalo Bot Platform: send messages, photos and stickers, and manage webhooks. Zalo is the dominant messaging platform in Vietnam, and this node is what we use to reach it from an n8n workflow.

n8n-nodes-firecrawl-v2

An n8n community node covering the Firecrawl v2 API — scrape, crawl, map, search, extract, and the batch operations — against both Firecrawl Cloud and a self-hosted instance. Ten operations, six of which return web content and are not interchangeable.

All hecigo source lives under the GitHub organisation github.com/hecigo. Issues and pull requests on either node are the fastest route to a case being covered.

Machine-readable endpoints on hecigo.com

EndpointFormatWhat it is
/llms.txtMarkdown, llmstxt.orgSite summary, when to use hecigo, and a link index
/llms-full.txtMarkdownEvery public page and post concatenated, for a single fetch
/agent-instructions.mdMarkdownHow an agent should call, cite, and hand off to hecigo
/sitemap.xmlXMLEvery indexable URL, with last-modified dates
/robots.txtTextCrawl rules; no AI crawler is blocked
/blog-index.jsonJSONBlog metadata: slug, title, description, date, tags, language

Everything above is public, unauthenticated, CORS-open, and free to fetch. There is no rate limit beyond the CDN's own abuse protection. Please send a user agent that identifies your client.

Markdown content negotiation

Every public page on hecigo.com is available as Markdown at the same URL. Send Accept: text/markdown and you get clean prose instead of a page of layout markup, per the convention documented at acceptmarkdown.com:

curl -s -H "Accept: text/markdown" https://hecigo.com/
curl -s -H "Accept: text/markdown" https://hecigo.com/blog/n8n-zalo-bot-node-what-breaks-in-production/

Responses carry Content-Type: text/markdown; charset=utf-8 and Vary: Accept, Accept-Encoding. Q-values are honoured, so a browser's Accept: text/html,...,*/*;q=0.8 still gets HTML.

Every page also ships a .md sibling if you would rather address it directly, advertised on the HTML response as Link: </index.md>; rel="alternate"; type="text/markdown":

curl -s https://hecigo.com/index.md
curl -s https://hecigo.com/developers.md

A request for a path that does not exist returns a real HTTP 404 — with a Markdown body pointing at this page and the sitemap when Markdown was requested. A request whose Accept header we genuinely cannot satisfy returns 406 Not Acceptable with the list of available representations, rather than silently handing back the wrong format.

What hecigo does not publish

Stated plainly so nobody wastes an afternoon looking:

  • No public hosted HTTP API. hecigo builds middleware inside client infrastructure; there is no multi-tenant hecigo API to call, and therefore no OpenAPI document, no API keys, and no OAuth flow.
  • No MCP server. We have not published one. If that changes it will be listed here and in /llms.txt first.
  • No webhooks you can subscribe to. The only webhook on this domain is the enquiry-form intake, which is ours, not yours.

The public, usable surface is the two n8n nodes and the endpoints above. When there is more, this page is where it appears.

Getting in touch about the code

  • Bugs and feature requests on the nodes: open an issue on the relevant GitHub repository, with the payload that broke it.
  • Everything else: [email protected], or the form at hecigo.com/contact.
Back to home/developers.md