MuleSoft Specialist for NetSuite-Salesforce Integration
Budget: $250 – $750 USD
I need a hands-on MuleSoft specialist to build a fresh integration that pushes and pulls data between NetSuite ERP and our other platforms—starting with Salesforce—while also squashing a few bugs in the existing flows.
Scope
• Create a compact, well-structured Mule 4 application in Anypoint Studio that connects NetSuite (token-based authentication) to Salesforce using REST/SOAP as required.
• Fix the specific bugs currently blocking two legacy flows so they run error-free again—mostly connector misconfigurations and timeout issues.
• Provide concise deployment notes so my in-house team can promote the package from sandbox to production.
Key tech
MuleSoft Anypoint Studio, REST/SOAP APIs, token-based auth, NetSuite, Salesforce. If you are comfortable extending to additional external REST APIs or internal apps later, that flexibility is a plus.
Deliverables
1. Source code and config files in a Git repo or ZIP.
2. Updated/working legacy flows with the identified bugs resolved.
3. Deployment guide and short hand-off call (optional but preferred).
This is our first engagement on a new integration, so I’m keeping the initial scope lean—proof that the flow works and the bugs are fixed. If it goes smoothly, more feature work will follow.
Scope
• Create a compact, well-structured Mule 4 application in Anypoint Studio that connects NetSuite (token-based authentication) to Salesforce using REST/SOAP as required.
• Fix the specific bugs currently blocking two legacy flows so they run error-free again—mostly connector misconfigurations and timeout issues.
• Provide concise deployment notes so my in-house team can promote the package from sandbox to production.
Key tech
MuleSoft Anypoint Studio, REST/SOAP APIs, token-based auth, NetSuite, Salesforce. If you are comfortable extending to additional external REST APIs or internal apps later, that flexibility is a plus.
Deliverables
1. Source code and config files in a Git repo or ZIP.
2. Updated/working legacy flows with the identified bugs resolved.
3. Deployment guide and short hand-off call (optional but preferred).
This is our first engagement on a new integration, so I’m keeping the initial scope lean—proof that the flow works and the bugs are fixed. If it goes smoothly, more feature work will follow.