Connects from Settings → Integrations · read-only · disconnect any time
What you get
What Fynex does with Asana
Fynex reads from Asana and does the finance work on top; it writes nothing back.
Tasks become jobs
Pick the project. Each task is something an invoice, a payment or a payout can be tied to — the unit the team already works in.
Changes by webhook
Fynex registers a webhook on the project; a renamed, moved or completed task reaches Fynex as it happens.
Money per task
What was invoiced, what was paid, what went out to a contractor — per task, without anyone copying numbers between tools.
Read only
Fynex reads the project and writes nothing back. Asana stays exactly as your team runs it.
How to connect
Connect it in three steps
Done once, from the dashboard, by whoever owns the account.
1
Approve Fynex
OAuth — you sign in to Asana and approve Fynex.
2
Choose the project that holds the work
Fynex lists what your account can see; pick the project that holds the work. One choice per connection, changeable later.
3
Let it run
Fynex registers a webhook on the project, so Asana reports task changes as they happen; a scheduled resync catches the rest.
Reads and writes
What Fynex reads, and what it writes
Read from Asana: tasks in the project you chose, with their fields and sections.
Written to Asana: nothing. This connection is read-only — Fynex keeps its own record of what happened to the money and shows it on the dashboard.
Project · Spring installsAsana
Harbor Ltd · refitcomplete · invoice paid
£4,200
Elm Studio · installin progress · invoiced
£1,850
Subcontractor · J. Reyestask done · payout due
£1,120
Task addedRidge & Co · survey
—
Security
How the connection is held
The same three rules on every connection Fynex makes.
OAuth, never a password
You approve Fynex inside the provider's own sign-in. Fynex holds an access token, not your credentials, and you can revoke it from either side.
Tokens encrypted at rest
Every connection token is stored encrypted (AES-256-GCM) with a key that never leaves the Fynex environment. One connection per business per provider.
Every write is logged
Where Fynex writes back, the write is recorded with what changed and why — only after the underlying event actually happened, never speculatively.
FAQ
Questions, answered
Through Asana's OAuth. From Settings → Integrations you sign in and approve Fynex, then choose the project that holds the work. The token is stored encrypted and one project is connected at a time.
The tasks in the project you chose, with their fields and sections. Each task becomes a job that invoices, payments and payouts are matched to. Fynex registers a webhook so changes arrive as they happen.
No. The Asana connection is read-only today. What happened to the money per task is kept in Fynex and shown on the dashboard.
One project per connection today. Connect the project a payment most naturally belongs to — usually the one you deliver client work in.
Yes, from Settings → Integrations, or by revoking Fynex in Asana. The webhook is removed and nothing in Asana changes.
We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.
Tasks stay in Asana — what each one earned and cost shows in Fynex
Essential cookies keep the site working. With your OK we also use analytics cookies (PostHog and Google) to see how the site is used and improve it. See our Cookie Policy.
