Oracle NetSuite and Asana integration

What moves between them

Purchase orders and vendor bills flow from NetSuite into Asana tasks and projects. Each NetSuite PO or vendor bill becomes a task in a designated Asana project, with the vendor name, amount, due date, and GL account stored in custom fields. On the Asana side, task status (not started, in progress, completed) can feed back to NetSuite via a separate polling cycle for status audits. Reference data such as vendors and GL accounts are synced first so custom field values reference real Asana dimension records. Webhook delivery from NetSuite Event Subscriptions is immediate; Asana webhook confirmations are returned within seconds.

How ml-connector handles it

ml-connector maintains separate OAuth 2.0 sessions for NetSuite and Asana, refreshing NetSuite tokens when they approach 60-minute expiry and keeping Asana Personal Access Token in encrypted storage. It subscribes to NetSuite Event Subscriptions for vendor bills and purchase orders at deployment time, verifying signatures against configured IP allowlist and shared secrets rather than HMAC (per NetSuite constraints). Each incoming event is transformed into an Asana task payload with vendor, amount, and GL account mapped to Asana custom fields. If the Asana API returns 429 rate-limit or 5xx errors, ml-connector backs off exponentially and retries the entire task creation, keying retries on the NetSuite event ID to avoid duplicates. Task status readback from Asana polls on a cadence you control, reconciles to NetSuite PO status fields, and records mismatches in the audit log. Every record transformation and delivery attempt is logged with timestamps and payloads.

A real-world example

A mid-market manufacturing company runs NetSuite as its ERP and uses Asana for procurement team coordination. Purchasing staff previously tracked purchase orders in NetSuite and created manual task summaries in Asana, leading to duplicate entry work and status mismatches when orders changed. With NetSuite and Asana connected, each purchase order and vendor bill approved in NetSuite automatically appears as a task in Asana the same day, tagged with the vendor and cost center so the procurement team sees real-time workload and financial context. When a vendor bill is received in NetSuite, Asana captures it as a task so reconciliation staff know what to match. The team marks tasks complete in Asana as goods arrive, and the completion status feeds into NetSuite audit fields for month-end reference.

What you can do

• •Sync NetSuite purchase orders and vendor bills into Asana tasks with vendor and GL account stored as custom field values.
• •Receive NetSuite Event Subscription webhooks, verify credentials against IP allowlist, and transform events into Asana task payloads.
• •Map NetSuite vendors and GL accounts to Asana custom fields so tasks carry full procurement and accounting context.
• •Poll Asana task status back to NetSuite to reconcile procurement progress and flag status disagreements in audit logs.
• •Authenticate both systems independently, manage OAuth token expiry, and replay failed syncs with built-in deduplication.

Questions

How does ml-connector handle NetSuite Event Subscription webhooks if there is no HMAC signature?

NetSuite Event Subscriptions do not include HMAC signatures; instead, security relies on IP allowlist and shared secret verification. ml-connector validates incoming payloads against the configured IP addresses and shared secret string before processing. It is your responsibility to restrict NetSuite's webhook sender IPs and keep the shared secret confidential.

What financial metadata does Asana carry if it has no native finance objects?

Asana has no invoice, PO, or GL account objects in its core data model. ml-connector stores financial context in Asana custom fields created for each Asana workspace, such as Vendor Name, PO Amount, Due Date, and GL Account Code. These fields are text, number, or date types depending on the metadata; the Asana UI displays them alongside task details.

What happens if Asana rate-limits or rejects a task creation?

ml-connector backs off with exponential jitter and retries the full task creation payload, keying on the NetSuite event ID so replayed events do not create duplicate tasks. Retries continue up to a configurable limit; permanent failures are logged in the audit trail with the full Asana error response so you can investigate and replay manually if needed.