Sage 50 and Asana integration

What moves between them

The main flow runs from Sage 50 into Asana. ml-connector polls Sage 50 for new and changed projects, purchase orders, and vendor records and creates or updates the matching Asana tasks and projects, writing the Sage reference (PO number, vendor ID, project code) into Asana custom fields so each work item ties back to its accounting record. Employee records can feed an Asana user reference for assignment. The return flow is status only: when an Asana task changes or completes, the signed webhook tells ml-connector, which updates the linked Sage record's reference or notes. Asana holds no finance objects, so ml-connector never writes invoices, payments, or GL entries from Asana into Sage.

How ml-connector handles it

Because Sage 50 has no cloud API, ml-connector runs a small Windows agent on the customer's machine that opens the company file through the SDK with the dedicated Sage username and password (and Application ID on US), then syncs to the platform over HTTPS. It must use a dedicated Sage user so the single-session file lock does not collide with someone working in Sage interactively, and the SDK version must match the installed Sage 50 year. On the Asana side ml-connector stores the token encrypted and sends it on every call, registers a webhook and completes the X-Hook-Secret handshake, then verifies the HMAC-SHA256 signature on each event. Sage 50 is pull-only, so its records are read on a schedule of five to fifteen minutes by comparing modified dates, since there is no cursor or event push. Sage projects map to Asana projects and Sage references map to pre-agreed Asana custom fields, resolved by field GID rather than name. Asana webhooks silently auto-delete after twenty-four hours of failed delivery, so ml-connector re-registers when one disappears, and because neither side offers idempotency keys, it checks for an existing record by reference and stores the Sage internal ID and Asana GID before creating to avoid duplicates. Failed calls back off and retry, and every record carries a full audit trail and can be replayed.

A real-world example

A regional construction subcontractor with about 80 staff runs Sage 50 on an office Windows server for job costing, vendor bills, and purchase orders, while project managers in the field track delivery and approvals in Asana. Before the integration, when a purchase order was raised in Sage 50 someone re-typed it into Asana as a task so the field team had something to action, and when the work was done nobody told the office, so bills sat unmatched at month-end. With Sage 50 and Asana connected, each new Sage purchase order and project becomes an Asana task carrying its PO number and job code, and when the project manager marks the task complete the status flows back to the Sage record. The double entry is gone and the office sees field progress without chasing it.

What you can do

• •Turn Sage 50 projects, purchase orders, and vendor records into Asana tasks and projects automatically.
• •Carry Sage references such as PO number, vendor ID, and project code in Asana custom fields so each task ties to its accounting record.
• •Read Sage 50 through a local Windows agent on the SDK and write Asana over its REST API, with both credential sets stored encrypted.
• •Receive Asana task change and completion events by HMAC-SHA256 signed webhook and write the status back to the linked Sage record.
• •Poll Sage 50 on a five to fifteen minute schedule, with retries and a full audit trail on every record, because Sage has no event push.

Questions

Why does Sage 50 need a local agent instead of a cloud connection?

Sage 50 is desktop software with no cloud REST API, so it can only be reached through a local SDK on the same Windows machine as the install. ml-connector runs a small agent there that opens the company file with a dedicated Sage username and password, then syncs to the platform over HTTPS. The machine has to stay on and logged in for syncs to run.

Which direction does data move between Sage 50 and Asana?

The main flow is Sage 50 into Asana, creating tasks and projects for Sage projects, purchase orders, and vendor work. The return flow is status only: Asana task changes and completions flow back to the linked Sage record. Asana has no invoice, payment, or GL objects, so ml-connector never writes financial entries from Asana into Sage.

How are Sage financial details represented in Asana when Asana has no finance objects?

Asana has no native invoice, purchase order, or GL account, so Sage references like PO number, vendor ID, and project code are carried in customer-defined Asana custom fields agreed up front. ml-connector resolves those fields by their GID rather than by name, since names can change, and maps Sage projects to Asana projects so the work stays grouped correctly.