When contract status changed in Oneflow, sync it to Fortnox.
Sync contract status updates from Oneflow to invoice/order records in Fortnox.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Fortnox Explore Fortnox →
TriggersFires when a new invoice is created in Fortnox.
Fires when a payment is recorded in Fortnox.
Fires when an invoice in Fortnox passes its due date unpaid.
Fires when a new expense is recorded in Fortnox.
Creates a new invoice in Fortnox.
Records a payment against an invoice in Fortnox.
Creates a new expense entry in Fortnox.
Syncs a customer's billing record in Fortnox.
Oneflow Explore Oneflow →
TriggersFires when a document is sent for signature in Oneflow.
Fires when all parties have signed a document in Oneflow.
Fires when a signer declines to sign in Oneflow.
Fires when a pending envelope in Oneflow is voided.
Sends a document out for signature via Oneflow.
Voids a pending envelope in Oneflow.
Checks a document's signing status in Oneflow.
Creates a reusable signing template in Oneflow.
More Fortnox + Oneflow workflows
See all Fortnox + Oneflow integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When contract status changed in Oneflow, sync it to Fortnox.” between Fortnox and Oneflow?
Yes — describe it in the box above and Knit's Integrations Agent researches Fortnox and Oneflow's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
What's the most common Accounting + E-Sign automation?
Creating an invoice or bill in Fortnox the moment a matching document is signed in Oneflow, so finance never has to manually re-key numbers from a signed PDF.
Can this trigger off a specific contract type, not every signature?
Yes — the Agent can filter on Oneflow's template, tags, or signer fields so only the agreements that actually need an Fortnox entry create one.