Frihet’s Original 46 Integrations and the Current Catalog
Frihet’s original 46-integration selection, reviewed against the status and scope published in the current product manifest.
Key takeaways
- This article preserves the original selection of 46 integrations as historical context
- The current manifest records 100 integrations with live status
- Each connector entry defines its scope; status alone does not imply a complete workflow
Contents
Frihet first published this content as a selection of 46 integrations for freelancers and small businesses. That number belongs to the article’s history, but it should not become a frozen list of promises. Connector status and scope change; the current sources are the product manifest and integrations directory.
In this review, the manifest contains 100 integrations with live status. It also records entries that are blocked, paused, or not implemented. That distinction matters: a visible catalog card does not necessarily mean a connection is available for an operational workflow.
What integration status means
Status answers a first question: can this connector be considered available? Its scope answers the next one. Two live integrations can have very different contracts. One may read records, another may export files, and another may synchronize one defined data type.
When evaluating an entry, check:
- current status, without inferring availability from its name;
- description, which summarizes the supported exchange;
- capabilities, when the manifest lists them;
- documentation, for authentication and configuration;
- flow direction, because reading and writing are not equivalent.
This approach prevents a focused connector from being presented as an end-to-end automation promise.
Payments and income
Frihet maintains live connectors in the payments category. When an entry does not declare detailed capabilities, do not infer that it reconciles collections, records fees, or changes states automatically.
Stripe Revenue Sync does have an explicit contract in the manifest: it imports Stripe payments as Frihet invoices every six hours. That description is enough to evaluate the specific flow. Before using imported records in a fiscal process, review account, client, currency, amounts, and tax fields.
Ecommerce
Shopify is live with published capabilities for reading orders, products, and customers, plus analytics. This scope can bring commercial data into Frihet; it does not say that every order issues an invoice or that tax decisions happen without review.
WooCommerce is also live, but its manifest entry does not enumerate a detailed contract. In that case, the connector documentation sets the boundary. Gumroad and Lemon Squeezy explicitly describe sales synchronization as income records. Keeping these differences visible makes the catalog useful instead of generic.
Automation
The directory includes live connectors for n8n, Zapier, and Make. Frihet also publishes a REST API with API-key authentication and 94 webhook event types with HMAC-SHA256 verification.
These parts let a team configure its own processes, but they do not create those processes by themselves. An event needs a defined later action; an action needs valid arguments; a sensitive write needs review. Document every step and test the flow with a narrow scope before expanding it.
Documents and communication
Google Drive is live with read-file and export-file capabilities. That supports a query or export flow, not a broad promise of automatic document archiving. Folder structure, naming, and permissions require separate logic that must be defined and checked.
Other communication connectors follow the same rule. Use the entry description, not behavior you expect from experience with another application. When an integration needs an external credential, record who manages it and how it can be revoked.
Banking: an important explicit exception
The available Frihet banking function starts with OFX, MT940, CAMT.053, and CSV statement imports. External direct bank connectivity is not active. A catalog entry must therefore not be described as direct bank synchronization or automatic daily import.
The supported flow is to obtain a statement, import it, review movements, and continue with the banking module’s tools. The wording is less dramatic, but it accurately describes what a business can plan around today.
From a historical selection to a governed catalog
The best way to preserve the value of the original 46 integrations is not to repeat old descriptions. It is to use that selection as a map of needs — payments, ecommerce, productivity, documents, and automation — and resolve each need against the current inventory.
Before connecting a tool:
- find its current entry;
- confirm that its status is
live; - read the exact scope;
- identify credentials and permissions;
- test with controlled data;
- review the result before making it part of the normal process.
The number shows the breadth of the catalog. Trust comes from something more important: each connector publishing its status and making no promise beyond what its contract can support.
Was this article helpful?
FAQ
Why does the title refer to 46 integrations?
This article began as a presentation of the original 46-connector selection. That historical reference remains, while the directory and manifest describe the current inventory.
How many integrations are live now?
The current product manifest records 100 entries with live status. It also distinguishes states that must not be treated as available.
Does live status guarantee any automation?
No. Live confirms connector availability, while its description, capabilities, and documentation define which data it can read, export, or synchronize.
How should I choose an integration?
Check status, scope, flow direction, credentials, and review points. Test with limited data and validate the result before expanding its use.
