[DOCS] Automate Opsgenie connector screenshots (#165265)

docs/management/connectors/action-types/opsgenie.asciidoc

@@ -15,6 +15,7 @@ or as needed when you're creating a rule. For example:
 
 [role="screenshot"]
 image::management/connectors/images/opsgenie-connector.png[Opsgenie connector]
+// NOTE: This is an autogenerated screenshot. Do not edit it directly.
 
 [float]
 [[opsgenie-connector-configuration]]
@@ -37,6 +38,7 @@ as you're creating or editing the connector in {kib}. For example:
 
 [role="screenshot"]
 image::management/connectors/images/opsgenie-params-test.png[Opsgenie params test]
+// NOTE: This is an autogenerated screenshot. Do not edit it directly.
 
 The Opsgenie connector supports two types of actions: Create alert and Close alert. The properties supported for each action are different because Opsgenie defines different properties for each operation.
 

x-pack/test/screenshot_creation/apps/response_ops_docs/stack_connectors/connector_types.ts

@@ -186,5 +186,18 @@ export default function ({ getService, getPageObjects }: FtrProviderContext) {
       await commonScreenshots.takeScreenshot('pagerduty-params-test', screenshotDirectories);
       await testSubjects.click('euiFlyoutCloseButton');
     });
+
+    it('opsgenie connector screenshots', async () => {
+      await pageObjects.common.navigateToApp('connectors');
+      await pageObjects.header.waitUntilLoadingHasFinished();
+      await actions.common.openNewConnectorForm('opsgenie');
+      await testSubjects.setValue('nameInput', 'Opsgenie test connector');
+      await testSubjects.setValue('secrets.apiKey-input', 'testkey');
+      await commonScreenshots.takeScreenshot('opsgenie-connector', screenshotDirectories);
+      await testSubjects.click('create-connector-flyout-save-test-btn');
+      await testSubjects.click('toastCloseButton');
+      await commonScreenshots.takeScreenshot('opsgenie-params-test', screenshotDirectories);
+      await testSubjects.click('euiFlyoutCloseButton');
+    });
   });
 }