HumationHuman + Automation
Back to Catalog

Export Zammad objects (users, roles, groups, organizations) to Excel

SirhexalotSirhexalot
972 views
2/3/2026
Random DataExampleData ManipulationCounterUtility
Official Page

This n8n workflow enables you to export data from Zammad, including Users, Roles, Groups, and Organizations, into individual Excel files. It simplifies data handling and reporting by creating structured outputs for further processing or sharing.

Features

  • Export Users with associated details such as email, firstname, lastname, role_ids, and group_ids.
  • Export Roles and Organizations with their respective identifiers and names.
  • Convert all data into separate Excel files for easy access and use.

Usage

  1. Import this workflow into your n8n instance.
  2. Configure the required Zammad API credentials (zammad_base_url and zammad_api_key) in the Basic Variables node.
  3. Run the workflow to generate Excel files containing Zammad data.

Issues and Suggestions

If you encounter any issues or have suggestions for improvement, please report them on the GitHub repository.

We appreciate your feedback to help enhance this workflow!

Export Zammad Objects (Users, Roles, Groups, Organizations) to Excel

This n8n workflow automates the extraction of various object types (Users, Roles, Groups, and Organizations) from Zammad and converts them into an Excel file. This allows for easy auditing, reporting, or migration of Zammad data.

What it does

This workflow performs the following steps:

  1. Manual Trigger: Initiates the workflow upon manual execution.
  2. Zammad API Calls:
    • Makes a series of HTTP requests to the Zammad API to fetch data for:
      • All users (/api/v1/users)
      • All roles (/api/v1/roles)
      • All groups (/api/v1/groups)
      • All organizations (/api/v1/organizations)
  3. Conditional Processing (If Node):
    • Checks if the Zammad API calls returned valid data (e.g., status code 200). If an API call fails, the workflow will not proceed to convert that specific object type.
  4. Data Transformation (Edit Fields):
    • For each successful API response, the data is prepared for conversion. This node likely renames fields or structures the data to be more suitable for an Excel spreadsheet.
  5. Convert to File (Excel):
    • Converts the processed data for each Zammad object type into individual Excel files.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Zammad Instance: Access to a Zammad instance.
  • Zammad API Token: A Zammad API token with sufficient permissions to read users, roles, groups, and organizations. This token will need to be configured as a Zammad credential in n8n.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Zammad Credentials:
    • In the "Zammad" node, select or create a new Zammad API credential.
    • Provide your Zammad instance URL and the API token.
  3. Execute the workflow: Click the "Execute workflow" button in the n8n editor to run the workflow manually.
  4. Download Excel Files: After successful execution, the generated Excel files will be available in the output of the "Convert to File" nodes. You can download them directly from the n8n interface.

Related Templates

Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack

🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.

nodaBy noda
52

Automated job scraping with SerpAPI, Gemini AI filter & email notifications

🛜 Daily Notification on Specific Latest Job Offers 🛜 🌟 Overview: Never miss a job offer again! This n8n workflow automates daily job scraping from LinkedIn, Indeed, Welcome to the Jungle, and more, using Google Dorks and SerpAPI. It filters offers with a Gemini AI agent, stores them in Google Sheets, and sends a sleek HTML newsletter to your inbox or subscribers—all manageable from your phone! 💼 Use Cases: Students hunting for M&A, valuation, or transaction services internships (6+ months). Career switchers seeking automated, curated job alerts. Content creators building a job newsletter to monetize their audience. ⚙️ How It Works: Scrape: Uses SerpAPI with a tailored Google Dork to fetch fresh job listings daily from top platforms. Filter: A Gemini AI agent validates offers to ensure they match corporate finance criteria. Store: Saves new offers in Google Sheets, marking duplicates to avoid spam. Notify: Generates an email/newsletter notification and sends it via Outlook 🛠️ Setup Instructions: Import the JSON workflow into n8n. Add credentials: SerpAPI (API key), Google Sheets (OAuth2), Microsoft Outlook (OAuth2) Customize the Google Dork in the "Edit Fields" node for specific job criteria. Schedule to run daily at 7 AM. Test and tweak the AI prompt for precision. 🔑 Required Credentials & Nodes: Credentials: SerpAPI, Google Sheets OAuth2, Microsoft Outlook OAuth2 Nodes: Schedule Trigger, HTTP Request, Google Sheets, AI Agent (Gemini), Microsoft Outlook 🔗 Creator: Louis Delahaye | n8n.io/creators/louisdl 🎥 YouTube @cash-routine My AI Agency : https://agence-alain.fr

LouisBy Louis
65

Seo blog content automation with GPT-4o-mini and human approval in Google Docs

Overview This n8n workflow automates the entire content creation process for SEO blog posts, from topic submission and AI drafting to human approval, revision, and final storage in Google Docs. It ensures high-quality, SEO-optimized content is generated efficiently while keeping a human in the loop for quality control. Prerequisites To use this workflow, you need the following accounts and credentials: Google Sheets Account: To manage the content tracker. The sheet must contain columns for Topic, Reference URL, Title, Status, and Link to document. OpenAI API Key (for GPT-4o-mini): To power the initial content drafting and subsequent revisions. Gmail Account: To send the content for human approval and wait for feedback. Google Docs Account: To create and store the final approved blog posts. How It Works The workflow operates in four main stages: Topic Submission, AI Content Creation, Human Approval & Revision Loop, and Final Publishing. Stage 1: Topic Submission and Tracking This stage captures a new blog topic and adds it to the content tracker. On form submission (Form Trigger): The workflow is initiated when a user submits a Topic and an optional Reference link through the form. Append row in sheet (Google Sheets): The new topic and reference link are added as a new row in your content tracker sheet. Get Topic from Google Sheets: The workflow fetches the newly added row, including the system-generated row_number for tracking updates. Stage 2: AI Content Creation (Initial Draft) The workflow uses an expert AI agent to generate the first draft of the blog post. Copywriter AI Agent: Acting as an expert SEO content strategist, the agent receives the topic and reference URL. The agent improves the provided topic into an SEO-optimized title. It writes a complete, conversational, SEO-friendly blog post (800–1200 words) using proper Markdown headings and lists. OpenAI Chat Model (GPT-4o-mini): Powers the agent's generation. Structured Output Parser: Ensures the output is in a JSON format with separate title and content keys. Set Data: The AI-generated title and content are mapped to workflow variables (Topic Title, Content) for easy use in subsequent nodes. Stage 3: Human Approval and Revision Loop This is the critical quality control step where a human reviews the draft and decides on the next action. Send Content for Approval (Gmail): The generated title and content are sent via email to the approver (<your email>). This uses a custom form that allows the user to choose Yes (Approve), No (Request Revision), or Cancel. The form also includes a Content Feedback textarea. Approval Result (Switch): The workflow pauses until the approver submits the form, and then directs the flow based on their choice. If "Yes" (Approved): Proceeds to the final publishing stage. The Update Topic Status on Google Sheets node is executed, setting the Status to Approved and logging the new Title. If "No" (Revision Requested): Proceeds to the revision loop. Copywriter Revision Agent: This agent takes the original content, the topic title, and the user's Content Feedback. It is instructed to incorporate the feedback, preserving the existing structure and tone, and outputs a revised blog post. The flow loops back through the Set Data node and then returns to the Send Content for Approval node for a new review. If "Cancel": Stops the workflow, and the Update Topic Status on Google Sheets node is executed. Stage 4: Final Publishing Once approved, the content is stored in Google Docs and the tracker is updated. Create Blog file (Google Docs): A new Google Doc is created using the approved Topic Title. Add blog content in file (Google Docs): The final Content (in Markdown format) is inserted into the newly created document. Update sheet with blog post link (Google Sheets): The final tracker update logs the Link to document and the Published date. Customization Tip Recommend using AI humanazier and AI detector tools before approval to make the SEO score better.

Priyanka RanaBy Priyanka Rana
528