MYOB and Pipedrive integration

What moves between them

The main flow runs from MYOB into Pipedrive. ml-connector polls MYOB for customer and contact changes, maps MYOB customers to Pipedrive organizations, and syncs contact information to Pipedrive persons. The sync runs on a schedule you define, typically daily or after new customers are created in MYOB. Pipedrive does not write accounting data back to MYOB, since Pipedrive has no GL, invoicing, or payment entities.

How ml-connector handles it

ml-connector stores the OAuth2 bearer token and company file credentials encrypted, refreshing the bearer token when it approaches expiry. On each sync cycle, it polls MYOB using OData $filter on LastModified to find new and changed customers since the last run. Each MYOB customer record is checked in Pipedrive by organization name or external ID, and new organizations are created or existing ones are updated with the latest data: name, address, phone, email, and custom fields. MYOB contact records (persons in MYOB terms) are synced to Pipedrive persons and linked to their parent organization. Rate limit handling respects MYOB's 8 requests per second and Pipedrive's token budget by batching reads and writes. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-market professional services firm uses MYOB for accounting and customer billing, and Pipedrive for its sales pipeline and deal tracking. Before the integration, the sales team manually entered new customers into Pipedrive after the account team set them up in MYOB, and contact updates were missed or duplicated. With MYOB and Pipedrive connected, each new customer created in MYOB flows into Pipedrive as an organization the next sync cycle. The sales team opens Pipedrive and sees current customer addresses, phone numbers, and invoice history all from MYOB, so they spend less time on data entry and more time selling.

What you can do

• •Read customers and contacts from MYOB using OAuth2 and company file credentials, with polling on a schedule you control.
• •Create MYOB customers in Pipedrive as organizations with name, address, phone, and email pre-filled.
• •Update Pipedrive organization and person records when MYOB customer or contact data changes, keeping sales records current.
• •Authenticate MYOB with OAuth2 and company file credentials (CF token refreshed on 401), and Pipedrive with API Token or OAuth2.
• •Track every sync with a full audit trail and replay failed records without manual re-entry.

Questions

Which direction does data move between MYOB and Pipedrive?

The main flow is MYOB into Pipedrive. Customer and contact records from MYOB are created or updated in Pipedrive. Pipedrive does not write data back to MYOB, since Pipedrive is CRM-only and has no accounting, invoicing, or GL capabilities.

How does ml-connector handle MYOB's polling-only API and the two-factor authentication requirement?

ml-connector stores the OAuth2 bearer token and company file credentials (CF username and password) encrypted, refreshing the token when it nears expiry. It polls MYOB on your schedule using OData $filter on LastModified to find changes since the last run, and presents both the bearer token and company file credentials on every call.

What happens when MYOB or Pipedrive rate limits are hit?

ml-connector respects MYOB's 8 requests per second and Pipedrive's token budget by batching reads and writes, and backs off with retries when rate limits are reached. If a batch fails, the sync is replayed from the audit log without data loss or duplication.