As part of Pipefy's roadmap evolution, we are initiating the transition of our current integrations infrastructure (Workato) to its next version, now native to the platform.
By the deadline communicated by Pipefy, integrations currently using Workato will be migrated to Pipefy's iPaaS.
This change is part of the evolution of Pipefy's integration platform and the consolidation of iPaaS as its strategic platform for connections with external products and systems.
Why is Pipefy making this change?
The migration is part of the evolution of Pipefy's integration architecture.
The goal is to bring the workflows currently executed in Workato to Pipefy's strategic integration platform, consolidating this experience within the product ecosystem.
What is Pipefy's iPaaS?
iPaaS is Pipefy's strategic platform for integrations and connections with external products. With this migration, workflows currently executed in Workato will now run on Pipefy's iPaaS.
Will I need to do anything?
Yes, in some steps.
Depending on the integration, customer involvement may be required to:
- Re-authenticate or provide third-party system credentials;
- Participate in or execute UAT (user acceptance testing);
- Validate data and results;
- Communicate any discrepancies;
- Formally approve the completion of the migration.
- Execute migration.
Will I need to involve my IT team?
This will depend on the characteristics of your integrations.
In some scenarios, it may be necessary to involve people responsible for third-party systems or credentials, especially when there is a need for re-authentication, technical validation, or specific adjustments.
The need for involvement will be identified by each customer during migration planning.
What happens if my integration needs changes?
Some integrations may require adaptations to work on the iPaaS.
Depending on the scenario, this may include implementation adjustments, component reconfiguration, workflow splitting, or changes to the integration logic. These cases will be identified during the migration process.
What happens if I don't migrate by then?
Integrations that have not completed the transition will stop working after the current infrastructure is decommissioned.
Will I have help from someone at Pipefy in this process?
Customers with dedicated support (CS/Managed Services) will have assistance for questions. Customers without a contracted service will have materials, training, and a support application to carry out the migration on their own.
Will I get training or support material?
In the coming weeks, Pipefy will provide guidance and support materials for those who will migrate on their own.
My company took months to approve the original connection (compliance/IT), will I have to redo this whole process?
Yes, connections need to be remade within the iPaaS.
