Skip to main content
Question

Integrating Zapier with Jira/Xray: I can create Tests, Test Sets & Test Executions and get the JWT from Xray API. What’s the correct way to link created Tests to a Test Set & Test Execution — REST endpoints or GraphQL?

  • September 11, 2025
  • 1 reply
  • 20 views

Integrating Zapier with Jira/Xray: I can create Tests, Test Sets & Test Executions and get the JWT from Xray API. What’s the correct way to link created Tests to a Test Set & Test Execution — REST endpoints or GraphQL?

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

  • Author
  • New
  • September 11, 2025

Integrating Zapier with Jira/Xray: I can create Tests, Test Sets & Test Executions and get the JWT from Xray API. What’s the correct way to link created Tests to a Test Set & Test Execution — REST endpoints or GraphQL?

Hi everyone 👋

 

I’m integrating Zapier with Jira/Xray and so far I’ve managed to:

 

  • Automatically create Tests, Test Sets, and Test Executions in Jira using the Jira Cloud connector.

  • Authenticate with the Xray Cloud API and successfully obtain the JWT using the /api/v1/authenticate endpoint.

 

Now I need to associate the newly created Tests with the Test Set and the Test Execution. I’m trying to do this with the following endpoints:

 

Add Tests to a Test Set

 

curl -X POST https://xray.cloud.getxray.app/api/v1/testset/TESTSET-123/test \
-H "Authorization: Bearer <TOKEN>" \
-H "Content-Type: application/json" \
-d '{
  "add": ["TEST-101","TEST-102"]
}'

Add Tests to a Test Execution

 

curl -X POST https://xray.cloud.getxray.app/api/v1/testexec/TESTEXEC-999/test \
-H "Authorization: Bearer <TOKEN>" \
-H "Content-Type: application/json" \
-d '{
  "add": ["TEST-101","TEST-102"]
}'

 

 

 My question: Is this the correct way to link existing Tests to a Test Set and a Test Execution?

Has anyone else built a similar workflow (creating issues from Zapier and then linking them with the Xray API), and could confirm if this is the recommended approach — or should I rather use GraphQL for this step?