Add HTTP workflow connector screenshots

[talboren]

Summary

• Adds screenshots for selecting and configuring the HTTP connector from Stack Management.
• Documents the workflow-editor connector-id autocomplete flow for creating or selecting a connector without leaving the editor.
• Keeps the existing connector-backed and direct URL syntax examples in the dropdown.

Testing

• Not run; docs-only change.

Made with Cursor

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: queued.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/workflows/steps/external-systems-apps.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[alaudazzi]

I left a few suggestions on the screenshots, mainly to enhance maintainability over time. Also, you might consider adding a stepper to the "Create an HTTP connector" section, which contains a series of sequential steps.
Check https://elastic.github.io/docs-builder/syntax/stepper/

[alaudazzi]

The text above describes well what can be set. This screenshot may not add much value.

[talboren]

@alaudazzi I find visual representation to always help - do you mind if we keep it?

[github-actions]

Docs review summary

Focus areas

• Style and clarity: Two minor violations — navigation path separator (> instead of →) and word choice (type instead of enter). Both have inline suggestions.
• Jargon: No issues.
• Frontmatter and applies_to: Existing frontmatter unchanged; no issues introduced by this PR.
• Content type fit: New section fits naturally within the existing how-to structure.
• Parent issue satisfaction: Not applicable (no linked parent issue).

Nits

• Lines 76 and 84 both open with "You can..." — tightening to a direct imperative ("Create an HTTP connector from...") would be slightly more concise, but it's not a blocker.

Notes

• Vale reported no findings for this file.
• Three new PNG screenshots were added but are not directly reviewable here; alt text in the Markdown is descriptive and meets accessibility requirements.

Generated by Docs review agent for issue #7047 · 36.4 AIC · ⌖ 6.43 AIC · ⊞ 10.7K

[talboren]

I left a few suggestions on the screenshots, mainly to enhance maintainability over time. Also, you might consider adding a stepper to the "Create an HTTP connector" section, which contains a series of sequential steps. Check https://elastic.github.io/docs-builder/syntax/stepper/

I find that more useful for "commandline" like steps? Do you have something specific in mind for how we can apply it? What would be the "steps"?