Connect Unifizeto your systems.
Plug-and-play integrations, custom integrations we build for you, or the Unifize API. Your teams and your systems stay in step.
Unifize, in the middle of your stack
Connect the systems your teams already use, so the work between them runs in one place. Built for ISO and FDA-regulated companies.
- SharePoint
- SAP
- Salesforce
- Slack
- SolidWorks
- Jira
- Microsoft Dynamics 365
- Oracle NetSuite
Pre-built, and ready from day one
Pre-built integrations for the tools your teams already work in. Connect them quickly, drop the manual work and see value from the first day.
SharePoint
Sync documents in real time, track updates and manage revisions.
Slack
Get notifications, create records and update checklists directly from Slack.
Email
Create records, track conversations and update checklists from email.
Scheduled CSV import
Automate bulk data imports into Unifize with scheduled CSV uploads.
SSO and SAML
Secure, central sign-in through your enterprise identity provider.
Standard integrations are currently in beta.
Connect, extend and automate with the API
Connect your systems, manage workflows and update data from your own code, and build integrations that work the way you do.
Keys are issued by our support team once your integration is registered.
Read the API docs (opens in a new tab)- OAuth 2.0 app tokens
- JSON over REST
- Testing environment
Built for you, for your ERP, CRM and CAD
For complex systems like ERPs, CRMs and CAD, we build the integration to fit your workflows and operations, from scoping to deployment.
ERP
The system that plans the business: parts, orders and suppliers.
CRM
The system sales and service run on.
CAD
The tools engineering designs in.
Project and issue management
The tracker engineering works from.
Turn your data into deeper insight
Export your Unifize data and join it with your other data streams, for cross-functional analytics in the BI tools your teams already rely on.
Power BI
Build real-time reports in Power BI to track quality performance by process, product or team.
Tableau
Create interactive dashboards in Tableau to uncover trends and see quality data at a glance.
BigQuery
Run complex queries in BigQuery and join Unifize data with other systems for deeper analytics.
A step-by-step approach to integration
A good integration starts with the business need. Scoping, development, testing and validation, so it launches smoothly and stays reliable.
01Pre-development
1 to 2 weeks
Define the scope, assess feasibility, gather the documentation and align stakeholders, so the integration's requirements are clear.
Before this phase
- Clear requirements and scope. Define the expected outcomes, the business logic and the systems to integrate.
- Access and documentation. Provide API credentials, system documentation and sandbox or test environment access.
- Stakeholder engagement. Name the key contacts, including internal teams and third-party vendors.
- Data governance and preparation. Clean, structured data with defined field mappings and transformation rules.
| Step | Hours | Done by |
|---|---|---|
| Define the requirement (outcome) | 4 to 8 | Day 2 |
| Define the structure on Unifize | 4 to 8 | Day 3 |
| Understand the structure on the source | 8 to 16 | Day 5 |
| Stakeholder identification and communication | 2 to 4 | Day 2 |
| Integration scope and boundaries | 4 to 6 | Day 4 |
| Data governance compliance | 4 to 8 | Day 5 |
| API rate limits and usage costs | 2 to 4 | Day 3 |
| Access to the docs | 2 to 4 | Day 2 |
| Read the docs (expert guidance) | 6 to 12 | Day 6 |
| Statement of data integrity | 4 to 6 | Day 4 |
| Authentication | 2 to 4 | Day 3 |
| Sandbox access | 2 to 4 | Day 5 |
| API keys and permissions | 2 to 4 | Day 3 |
| Risk analysis | 4 to 8 | Day 6 |
02Development
3 to 4 weeks
Configure the APIs, implement the workflows, map the data fields and build the error-handling logic.
Before this phase
- Technical resources. Confirm API access, rate limits and data integrity policies.
- Environment setup. Configure the Unifize sandbox, set up authentication and test API connectivity.
| Step | Hours | Done by |
|---|---|---|
| Unifize sandbox setup | 4 to 8 | Day 5 |
| Architecture planning | 6 to 12 | Day 7 |
| Field mapping | 8 to 12 | Day 10 |
| Technical design (workflows, logic) | 8 to 16 | Day 12 |
| Data transformation logic | 8 to 16 | Day 12 |
| Error handling logic | 6 to 12 | Day 10 |
| Write the code | 24 to 60 | Day 20 to 30 |
03Testing and launch
1 to 2 weeks
Validate the functionality, run user acceptance testing, write the documentation and deploy with minimal disruption.
Before this phase
- Testing requirements. Allow time for user acceptance testing (UAT) and write a testing plan.
- Launch planning. Define the approval process and deployment steps, and schedule around freeze periods.
| Step | Hours | Done by |
|---|---|---|
| Test case creation | 6 to 10 | Day 30 |
| Test phase | 8 to 16 | Day 35 |
| Launch plan | 4 to 8 | Day 37 |
| Documentation | 6 to 10 | Day 38 |
| End-user training | 4 to 8 | Day 40 |
| Post-launch monitoring | 4 to 8 | Day 50 |
| Live issue handling | 6 to 12 | Day 60 |
04Maintenance
Ongoing
Monitor the integration's performance, resolve issues and tune it for long-term reliability.
Before this phase
- Support and monitoring. A plan for issue resolution, performance tracking and regular health checks.
| Step | Hours | Done by |
|---|---|---|
| Ongoing monitoring and health checks | 4 to 8 | After launch |
Shortest run Longest runDays count from kickoff. Hours are a lower to upper estimate.
Frequently asked questions
What is the difference between standard integrations and custom integrations?
Standard integrations are pre-built, plug-and-play connections to common tools like Slack, SharePoint and Power BI. They need minimal setup and can be used right away.
Custom integrations are built to fit enterprise systems like SAP, Salesforce and CAD software. They need requirement mapping, development, testing and deployment so they match your business needs.
How long does it take to implement a custom integration like Salesforce or SAP ERP?
It depends on the integration's complexity, the data volume, the business rules and the API's availability.
Most custom integrations take 2 to 3 business months, covering requirement mapping, development, testing and deployment. Projects with complex data mapping or several systems can take longer.
What are the integration methods available in Unifize?
Unifize supports three integration approaches:
- One-way sync
- Data flows in one direction, for example importing records from SAP into Unifize.
- Master data sync
- Keeps key datasets like users, parts or suppliers consistent across platforms.
- Two-way sync
- Data flows both ways in real time, so both systems stay current.
How does email integration work in Unifize?
You can send and receive email inside process records. Emails can also be forwarded into Unifize to create new records, so every conversation stays linked to its workflow.
Can Unifize update records based on incoming emails?
Yes. Unifize can parse an email's content to update checklist metadata, statuses or field values, which cuts manual data entry.
What level of IT involvement is required for custom integrations?
Your IT team works with ours to provide API access, define the business rules and test the workflows. Unifize manages the development and deployment.
How do I get API keys for integrating with Unifize?
API keys are not self-service. Contact Unifize support to register your integration, confirm the requirements and receive your credentials.
Are integrations included in Unifize’s one-time implementation cost?
No. Integrations are scoped separately, with their own timeline and cost depending on the scope, the type of integration and its complexity.
Anything else? Write to sales@unifize.com.
Bring the system you need connected.
Bring the system and the process that depends on it, and we will map the integration with you in a 30-minute walkthrough.