topic How to do performance testing in Workato? in Workato Pros Discussion Board

How to do performance testing in Workato?

vinaya — Fri, 11 Apr 2025 04:23:33 GMT

Hi Experts,

We’re planning to conduct performance testing on our Workato platform and wanted to check if there’s any in-house documentation or guidance available. Specifically, we’re looking for information related to performance metrics, CPU usage, response times, as well as details on load, stress, and volume testing.

Any pointers or resources would be greatly appreciated!

Thanks in advance.

Re: How to do performance testing in Workato?

Prudvi — Tue, 15 Apr 2025 12:53:56 GMT

@gary1 & @shivakumara - Could you please help.
Regards,
Prudvi

Re: How to do performance testing in Workato?

gary1 — Tue, 15 Apr 2025 17:40:11 GMT

I think more details are needed to be helpful. Workato is pretty big, so narrowing the scope to specific components or functionality would be a good start.

"We want to use the API platform to support 1 million credit card transactions per day" is a lot different than "We want to use Workato to send 1 million emails per day". Both have high volume requirements, but the underlying components are very different.

Also, stress testing Workato (with a task-based pricing model) sounds expensive!

Re: How to do performance testing in Workato?

shivakumara — Wed, 16 Apr 2025 13:27:32 GMT

@Prudvi @vinaya ,
Ideally, we need following parameters to give better solution.
Use Case or Scenario:
Clearly define the business problem or automation scenario you're addressing, outlining the key objectives and expected outcomes.
Applications & API Interactions:
List all applications involved in the integration, including any API endpoints being consumed or exposed as part of the solution.
Loops & Data Traversal:
Specify the types of loops used (e.g., For Each, While, or batching strategies) to process items efficiently within your workflow.
Solution Design Quality:
Highlight best practices implemented such as modular architecture (loose coupling), robust error handling strategies, use of reusable components (e.g., callable recipes or functions), and considerations for scalability and maintainability.

Here are some suggestions:
Workato provides key runtime insights:
-------------------------------------------------------
Job Execution Time (start → end)
Recipe Performance (success/failure count, job duration)
API Response Time (via HTTP action logs)
Queue length and delays (if using Workato Queues)

You can access these through
Recipe Reports (Dashboard)
Job History
Insights Reports (if enabled)
---------------------------------------------------------------------

--> Capture Performance Logs

Use Recipe Functions + Lookup Tables or Data Store to track:
job_id
start_time, end_time
duration
payload_size
response_time (for API calls)
status (success/failure)

You can then send this data to for further actions
Google Sheets
Snowflake
------------------------------------------------------------------
Note: Use External application like Postman to run the load testing (Stress, Volume) but remember it involve huge tasks consumptions --> high cost for the company.

Thanks and Regards,
Shivakumara K A