Integrations That Reduce Manual Work: 2026 Guide
How to choose payment, ecommerce, document, and automation integrations by status, published scope, and review process.
Key takeaways
- Choose each connector by its published scope, not only by its name
- Frihet supports OFX, MT940, CAMT.053, and CSV statement imports for reviewed banking workflows
- APIs, webhooks, and automation platforms solve different integration needs
Contents
An integration is useful when it removes unnecessary transcription without hiding which data enters, which data leaves, and who confirms the result. Choosing by logo alone can create expectations that the connector does not meet. Choosing by contract helps you design a workflow you can review and maintain.
Frihet publishes an integrations directory with a status for each connector. That status is the starting point: a live integration is available, while other states mean you should not base an operational process on it. The connector entry then defines its scope and links to relevant documentation.
Start with the data you want to move
Before enabling anything, describe the flow in one concrete sentence: “I want to inspect orders,” “I want to import collections,” “I want to export a document,” or “I want an event when an invoice changes.” That sentence separates four mechanisms:
- Native connector: handles a defined exchange with a particular tool.
- File import: brings in data that you exported from another source.
- API: lets custom software read or write documented resources.
- Webhook: informs another system when an event occurs.
A shared name does not make these mechanisms interchangeable. A connector that reads orders does not imply invoice issuance; a document exporter does not imply automatic archiving; a webhook does not execute the rest of a process by itself.
Payments: separate import from reconciliation
Frihet records Stripe Revenue Sync as live. Its published contract imports Stripe payments as Frihet invoices every six hours. This is a specific flow: check the connected account, inspect imported records, and verify fiscal fields before continuing the invoicing cycle.
The directory includes other payment connectors. For each one, read its current entry rather than transferring Stripe Revenue Sync behavior to a different integration. A live status confirms availability, while its description and documentation determine the resources it reads or writes.
Banking: the available flow starts with a statement
Frihet does not currently provide external direct bank connectivity. The live function is bank statement import for OFX, MT940, CAMT.053, and CSV files. The importer includes bank presets, deduplication, and an interface for reviewing transactions.
This creates a clear boundary: you obtain the file from your financial institution, import it, and verify the result. You can then categorize or match movements inside the banking module. Do not design a workflow that depends on an automatic daily sync because that is not the published contract.
Ecommerce: read each connector’s scope
The Shopify integration is live, and its published capabilities cover reading orders, products, and customers, plus analytics. This can bring commercial context into Frihet, but it does not justify promising that every order issues an invoice, calculates tax, or changes a payment state without review.
WooCommerce is also listed as live. When the manifest does not specify a detailed capability, use the connector entry and documentation as the reference. Gumroad and Lemon Squeezy declare sales synchronization as income records. Preserving these distinctions prevents an automation from being built on an assumption.
Documents and communication
Google Drive is live with read-file and export-file capabilities. Wording matters: “export a file” is not the same as “automatically archive every document.” If you need a particular folder structure, naming convention, or permission model, define and test that logic separately.
Communication and productivity connectors follow the same rule. Verify the incoming event, available action, and transferred fields. When an integration relies on external credentials, document who can revoke them and what happens when they expire.
APIs, webhooks, and automation
Frihet publishes a REST API with API-key authentication and 94 webhook event types with HMAC-SHA256 verification. It also maintains live connectors for n8n, Zapier, and Make. These surfaces let you build custom workflows without attributing an unconfigured sequence to the ERP.
A controlled workflow is implemented in stages:
- define one input event;
- use test data or a limited scope;
- inspect the payload and identifiers;
- add the next action only after the previous one is stable;
- require review before accounting changes or external sends;
- record failures and a recovery path.
Integration evaluation checklist
- Confirm that the current status is
live. - Read the scope and direction of the flow.
- Identify required credentials and permissions.
- Test with a small set of data.
- Review duplicates, currency, tax fields, and identifiers.
- Decide which steps require approval.
- Document how to stop or revoke the connection.
Integrations reduce manual work when their contract is clear and the process retains control points. The goal is not to connect everything. It is to connect what you can verify, safely and deliberately.
Was this article helpful?
FAQ
How do I know what an integration does?
Read its entry in the integrations directory. The current status and description define its scope; do not assume that a connector imports, transforms, or writes data that its contract does not list.
Does Frihet connect directly to my bank?
External direct bank connectivity is not active. The available workflow is to import OFX, MT940, CAMT.053, or CSV statements and review the transactions in Frihet.
Can I automate a custom process?
Frihet provides a documented REST API, 94 webhook event types, and live connectors for automation platforms. Configure and test each workflow with controlled data before using it in production.
Do all integrations behave the same way?
No. Some read data, some export information, and others expose specific actions. Check capabilities, flow direction, and authentication requirements in the relevant connector entry.
