diff --git a/docs/modules/ROOT/pages/how-to-guides/testing_applications/proc_creating_custom_test.adoc b/docs/modules/ROOT/pages/how-to-guides/testing_applications/proc_creating_custom_test.adoc
index 6347e194..09373034 100644
--- a/docs/modules/ROOT/pages/how-to-guides/testing_applications/proc_creating_custom_test.adoc
+++ b/docs/modules/ROOT/pages/how-to-guides/testing_applications/proc_creating_custom_test.adoc
@@ -91,6 +91,15 @@ spec:
 . Add your new custom test as an integration test in {ProductName}.
 .. For additional instructions on adding an integration test, see this document: xref:how-to-guides/testing_applications/proc_adding_an_integration_test.adoc[Adding an integration test].
 
+. Params/Labels added by integration-service automatically to the integration PipelineRun
+----
+.. A param containing the Snapshot as a json string
+.. A param containing the DeploymentTarget connection details and Environment name
+.. A Label for type of PipelineRun, i.e. "test"
+.. A Label for optional flag of IntegrationTestScenario 
+.. Labels For the name of application , component and IntegrationTestScenario
+----
+
 .Verification
 
 After adding the integration test to an application, you need to trigger a new build of its components to make {ProductName} run the integration test. Make a commit to the GitHub repositories of your components to trigger a new build.