Quick Overview This workflow collects a URL via an n8n Form, follows HTTP redirects to the final destination, extracts page and Open Graph/Twitter metadata from the final HTML, and displays the results back in a form response using only built-in n8n nodes. How it works Receives a URL submission from the n8n Form trigger. Normalizes the input so it includes an http/https scheme. Requests the URL with redirect-following disabled to capture the HTTP status and Location header. If the response is a redirect (301/302/307/308), tracks visited URLs and redirect count, detects loops or exceeding the redirect limit, and either continues to the next Location URL or shows a redirect/loop error. If the response is 200 OK, parses the HTML to extract the title, meta description, canonical URL, language, Open Graph tags, Twitter Card tags, and common tracking parameters. Displays the extracted metadata and final URL in a results form, then redirects back to the input form page. Setup Activate the workflow so the n8n Form trigger has a Production URL.
Tags
Related workflows
See all General Automation→Track data deletion requests from Gmail with Jira, BigQuery, and Slack
Quick Overview This workflow monitors a Gmail inbox for potential privacy/data deletion requests, classifies each email, creates the appropriate Jira issue, logs a minimal audit record to BigQuery, and alerts the team in Slack, with an optional Gmail confirmation draft for human review. How it works Triggers when a new email matching deletion-related keywords arrives in Gmail (or runs manually for testing). Loads shared configuration values like Jira project details, BigQuery destination, SLA window, Slack channel, and confidence threshold. Cleans the email text, extracts the requester address, classifies the request type (deletion/access/correction), and calculates an SLA due date with a confidence score. Creates a Jira task for the privacy team when the classification is confident, or creates a separate Jira task labeled for manual review when it is not. Inserts an audit row into Google BigQuery with metadata such as request type, confidence, received time, due date, and whether a Jira issue was created. Posts a Slack message to the configured channel about the routed request or the need for manual review. Creates a draft confirmation email in Gmail for the requester after a rout
Draft security questionnaire answers with Notion, Google Docs, and Slack
Quick overview This workflow runs on demand to match security questionnaire questions against an approved-answer library in Notion, then creates a Google Docs draft and notifies reviewers in Slack, optionally updating a Notion tracker page. How it works Starts manually to run a test questionnaire and load configuration values like the Notion database ID, Google Drive folder ID, and confidence threshold. Loads a list of questionnaire questions and queries the Notion database for answers whose Status equals the configured approved value. Compares each questionnaire question to the approved Notion questions, selects the closest match, and marks low-confidence matches as “Needs review” instead of auto-answering. Branches based on whether any answers need review and posts a corresponding Slack notification to the configured review channel. Builds a formatted draft body containing each question, match confidence, owner, and either the approved answer or a “Needs review” placeholder. Creates a new Google Docs document for the draft and optionally updates a Notion questionnaire tracker page with “Draft ready for review” and the needs-review count. Setup Add Notion credentials and set the a
Draft incident postmortems with PagerDuty, Confluence, Slack and Google Sheets
Quick overview This workflow creates a Confluence postmortem draft for resolved PagerDuty incidents, then notifies the incident owner in Slack and optionally logs the draft in Google Sheets. How it works Triggers manually for testing or receives a PagerDuty webhook when an incident is resolved. Loads shared configuration values like PagerDuty and Confluence URLs, Confluence space and parent page, Slack channel, and optional Google Sheets settings. Normalizes the incoming incident payload and fetches the incident details and log entries from the PagerDuty API. Builds an HTML postmortem draft containing an incident summary, placeholders for impact and root cause, a basic timeline, and action-item prompts. Creates a new Confluence page under the configured parent page using the generated postmortem content. Posts a Slack message to the configured channel and optionally appends a row to a Google Sheets “Postmortems” tab with key incident metadata. Setup Add PagerDuty API credentials to the PagerDuty HTTP Request steps and configure a PagerDuty webhook pointing to this workflow’s webhook URL for resolved incidents. Add Confluence (Atlassian) credentials and set your Confluence base URL,