Zapier, Make, Pabbly Connect and n8n

hectile.com/app/settings/integrations

Settings

OrganizationBrandsTeamFeaturesGSTTaxesPayment InstructionsNumberingDocument DesignRemindersOnline PaymentsEmail SendingDevelopersIntegrationsBillingUsage

Connect Hectile to the tools you use

ZZapierConnect with an API keyHow to Connect

MMakeConnect with an API keyHow to Connect

PPabbly ConnectConnect with an API keyHow to Connect

nn8nCommunity node · API keyHow to Connect

#SlackConnected · #salesSettings

Zapier · Paid invoices to the teamActive

HTrigger · Hectile
Invoice paidOn

SAction · Spreadsheet
Add a row: number, customer, amount, date

#Action · Team chat
Post “Lakeview paid ₹2,47,800” in #sales

↻ Replay

1. Turn on the apps

   Settings → Features → Connections (Business, with API and webhooks).

2. Create an API key

   Settings → Developers, with only the access the automation needs.

3. Settings → Integrations → How to Connect

   Steps for Zapier, Make, Pabbly Connect or n8n.

4. Build your automation

   Pick a Hectile trigger or action in the app.

When a trigger runs

• Zapier checks Hectile for new events on your Zapier plan's schedule — every 1 to 15 minutes, depending on the plan. That's how often Zapier looks, not a promise of when a Zap runs: it runs after the change, not the moment it happens. Each event runs a Zap once: Zapier remembers its Event ID, so one customer changed twice is two runs, and checking again never runs an event twice. Every Zap checks on its own.
• Each check reads the newest 1,000 events of its kind from the last 24 hours. When you turn a Zap on, or back on, it starts with what happens next — not what happened while it was off.
• If a check fails — Hectile briefly unreachable, or a key that needs reconnecting — Zapier shows the error and checks again. The next check that works picks up what it missed, once, if it is still among those newest 1,000 events from the last 24 hours. A larger burst (a big import, say) or checks failing for longer can leave older events out, and those aren't sent to the Zap later.
• A check that can't finish within Zapier's limits for one check — Hectile slow to answer, or very large documents among those events — shows an error and Zapier checks again; it never counts only some of them. Very large documents can make that error repeat until they're older than 24 hours or no longer among the newest 1,000.
• Zapier's own limits are separate: if 100 or more new events arrive in one check, Zapier holds those runs in Zap history for you to look at before they run, and every run uses tasks from your Zapier plan.
• Make, Pabbly Connect and n8n are told about each event as it happens.
• In a Hectile action, map the trigger's Event ID to Unique ID, so a step that runs again makes one record and two events always make two. Steps in other apps don't get this from Hectile: one can run twice — for example when Zapier retries it or you replay a run.

To disconnect an app, revoke its API key.