Preparation before a job interview usually follows the same pattern: read the resume, lay the job profile next to it, put together a few questions, often shortly before the appointment and with varying thoroughness depending on the interviewer. The Interview Route takes this part off your hands. As soon as a calendar entry with the prefix "Interview:" is created, the workflow loads the candidate profile and the corresponding job description from the recruiting tool and builds a question set of 12 to 15 questions in the categories of technical competence, soft skills and cultural fit.
\nThe question set is stored in the note tool together with candidate, position and date, and the interviewer receives an email with a link and a short candidate summary. The five most important questions are flagged, along with notes on what to look for in the answers. What gets automated is the gathering and drafting, not the evaluation: the actual conversation and the assessment of the candidate remain with the interviewer.
\nFor Voyage, this workflow is more of a complement in the HR domain than a core offering, but it illustrates well how a recurring preparation step with clear inputs (profile, job description) can be automated cleanly.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: interview-route.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Trigger: new interview appointment", "beschreibung": "A calendar entry titled with the prefix \"Interview:\" starts the workflow.", "rolle": "mensch" }, { "nr": 2, "titel": "Load candidate and position", "beschreibung": "Profile and corresponding job description are pulled from the recruiting tool (ATS).", "rolle": "automatisch" }, { "nr": 3, "titel": "Generate question set", "beschreibung": "12 to 15 questions across three categories are created, with the top 5 flagged and notes on possible red flags.", "rolle": "automatisch" }, { "nr": 4, "titel": "Save in the note tool", "beschreibung": "The question set is stored together with candidate, position and date.", "rolle": "automatisch" }, { "nr": 5, "titel": "Notify the interviewer", "beschreibung": "An email with a link to the question set and a short candidate summary is sent.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Tailored question set", "text": "The questions are matched to the candidate and the position, not generic." }, { "titel": "Comparable structure", "text": "Technical competence, soft skills and cultural fit are covered in the same structure for every interview, regardless of who conducts it." }, { "titel": "Less manual gathering", "text": "Profile and job description are loaded automatically instead of being pulled together by hand for every conversation." } ], "voraussetzungen": [ { "label": "Calendar tool", "text": "Google, Outlook or Calendly as the trigger, with the candidate ID stored in the appointment.", "icon": "calendar_month" }, { "label": "Recruiting tool or ATS", "text": "Personio, Greenhouse or Lever for profile and position.", "icon": "badge" }, { "label": "Note tool", "text": "Notion, Evernote or OneNote for the question set.", "icon": "description" }, { "label": "LLM access and email delivery", "text": "API access for OpenAI, Claude or Gemini, plus Gmail or Outlook for the notification.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test interview", "text": "Create a calendar event with a candidate ID and an interviewer.", "icon": "event" }, { "label": "Data retrieval", "text": "Check whether profile and job description were loaded completely from the ATS.", "icon": "download" }, { "label": "Question set", "text": "Check whether 12 to 15 questions across three categories are produced, with the top 5 and red flags flagged.", "icon": "fact_check" }, { "label": "Edge cases", "text": "Test different roles, a missing candidate ID and panel interviews.", "icon": "rule" } ], "goLive": [ { "label": "Approval to start", "text": "Activate the workflow only once data retrieval, the question set and the notification run cleanly.", "icon": "check_circle" }, { "label": "Standard template", "text": "Define how candidate, position, date and categories are laid out in the question set.", "icon": "article" }, { "label": "Candidate ID as a required field", "text": "Set up the ID format in the recruiting tool as binding.", "icon": "badge" }, { "label": "Feedback loop", "text": "Regularly ask which questions were most helpful in the actual conversation.", "icon": "rate_review" } ], "haeufigeFehler": [ { "label": "Candidate ID missing from the event", "text": "Set up a template or a required field in the recruiting tool.", "icon": "tag" }, { "label": "Position not linked", "text": "Check the mapping in the ATS.", "icon": "link_off" }, { "label": "Interviewer email not extracted", "text": "Set a filter on internal domains.", "icon": "alternate_email" }, { "label": "Storage fails", "text": "Check write access and the template in the target database.", "icon": "lock" } ] }, "arbeitsprompts": [ { "titel": "Interview Question Generator", "beschreibung": "Creates a structured question set from the candidate profile and job description, with 12 to 15 questions across the categories of technical competence, soft skills and cultural fit.", "prompt": "You are an experienced HR professional and should create a personalized interview question set.\n\n**Candidate information:**\n- Name: [CANDIDATE_NAME]\n- Position: [POSITION]\n- Experience: [WORK_EXPERIENCE]\n- Special qualifications: [QUALIFICATIONS]\n\n**Job description:**\n[JOB_DESCRIPTION]\n\n**Task:**\nCreate a structured interview question set of 12 to 15 questions, divided into the following categories:\n\n1. **Technical competence** (5 to 6 questions): questions on technical skills and experience, tailored specifically to the job requirements and the candidate's resume.\n\n2. **Soft skills and working style** (4 to 5 questions): behavior based questions on teamwork, communication and problem solving.\n\n3. **Cultural fit and motivation** (3 to 4 questions): questions on values, workplace culture preferences and motivation for the position.\n\n**Format:**\n- Each question with a brief note on why it is relevant.\n- Flag the five most important questions.\n- Add notes on possible red flags in the answers." } ], "prompt": "GOAL\nBuild a workflow that, for every new interview appointment, automatically loads the candidate profile and job description, creates a personalized question set of 12 to 15 questions from them, stores it in the note tool, and notifies the interviewer.\n\nAdapt the structure to the concepts of your automation tool (for example nodes, steps, zaps or agent actions). While doing so, preserve the trigger logic, the sequence and the data flow.\n\nTRIGGER\nType: new calendar event with the title prefix \"Interview:\".\nFilter: the event must contain the candidate ID, this is the required field convention in the recruiting process.\n\nSTEPS\n1. Load candidate and position: read the candidate ID and the job ID from the event description, and use them to retrieve the candidate profile (work experience, qualifications) and the linked job description from the ATS (Personio, Greenhouse or Lever).\n2. AI step: generate the question set. Use the following prompt unchanged (see PROMPT below). Output: 12 to 15 questions across three categories, with the top 5 flagged and notes on possible red flags.\n3. Save: store the question set in the note tool (Notion, Evernote or OneNote), together with candidate, position and interview date.\n4. Output: notify the interviewer, whose address you filter from the event's internal attendee list, by email with a link to the question set and a short candidate summary.\n\nPROMPT (use exactly as is)\n\"\"\"\nYou are an experienced HR professional and should create a personalized interview question set.\n\n**Candidate information:**\n- Name: [CANDIDATE_NAME]\n- Position: [POSITION]\n- Experience: [WORK_EXPERIENCE]\n- Special qualifications: [QUALIFICATIONS]\n\n**Job description:**\n[JOB_DESCRIPTION]\n\n**Task:**\nCreate a structured interview question set of 12 to 15 questions, divided into the following categories:\n\n1. **Technical competence** (5 to 6 questions): questions on technical skills and experience, tailored specifically to the job requirements and the candidate's resume.\n\n2. **Soft skills and working style** (4 to 5 questions): behavior based questions on teamwork, communication and problem solving.\n\n3. **Cultural fit and motivation** (3 to 4 questions): questions on values, workplace culture preferences and motivation for the position.\n\n**Format:**\n- Each question with a brief note on why it is relevant.\n- Flag the five most important questions.\n- Add notes on possible red flags in the answers.\n\"\"\"\n\nDATA FLOW\nTrigger to step 1: candidate ID and job ID from the event description, interviewer address from the attendee list.\nStep 1 to step 2: candidate profile (name, work experience, qualifications) and job description.\nStep 2 to step 3: finished question set.\nStep 3 to step 4: link to the question set. Trigger to step 4: interviewer address.\n\nERROR HANDLING\nCandidate ID missing from the event: stop the run and send a note to the recruiting team. Establish the ID convention as a required field or template in the calendar event.\nPosition not linked to the candidate: check the ATS mapping. Without a job description, do not generate a generic question set, escalate the case to the recruiting team instead.\nInterviewer address not extractable: filter the attendee list on internal domains. For panel interviews, notify all internal attendees.\nStorage in the note tool fails: check write access and the target database or template.\nData protection: store candidate data only in the internal note tool, without passing it on to external channels.\n\nPLACEHOLDER CONVENTION\nAll placeholders in square brackets in the prompt are mapped fully dynamically from the ATS, as described in the data flow. There are no prompt placeholders that require manual input. What you configure manually is only the calendar filter (title prefix \"Interview:\"), the ATS access, the destination in the note tool and the internal mail domain.\n\nSELF CHECK BEFORE COMPLETION\nCheck, before you report the workflow as finished:\n1. Are all steps connected correctly, and does the calendar filter catch the title prefix \"Interview:\"?\n2. Is the prompt inserted completely and unchanged, and are all ATS fields mapped correctly?\n3. Is the question set stored with candidate, position and date, and does the email go exclusively to internal interviewers?\n4. List all points that require manual configuration: the format of the candidate and job ID in the appointment, ATS access, the destination in the note tool, the internal mail domain, LLM access.", "einrichtung": { "intro": "Two routes lead to the same result. Pick the one that fits your setup.", "varianten": [ { "variante": "Builder-Prompt", "einleitung": "Suitable when you want to build the workflow in your own automation tool.", "schritte": [ "Open your workflow tool, for example n8n, Make, Zapier or Langdock.", "Create a new workflow and give it a name.", "Choose the AI-assisted build option if your tool offers one.", "Paste the builder prompt from above in full.", "Check the result against the step sequence in this document, then add your access credentials and channels." ] }, { "variante": "JSON-Import", "einleitung": "Suitable when you want to take the workflow over unchanged.", "schritte": [ "Download the JSON file from the JSON export section.", "Open the workflow area of your tool and create a new workflow.", "Give it a name and confirm.", "Open the menu on the workflow name and choose to import a JSON file.", "Upload the file, then add your own access credentials.", "Run a test before you activate the workflow." ] } ] }, "exportMeta": { "datei": "w08_interview-route__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Interview-Route", "beschreibung": "Lädt bei jedem neuen Interview-Termin automatisch Kandidatenprofil und Stellenbeschreibung, erstellt daraus einen strukturierten Fragenkatalog, legt ihn im Notiz-Tool ab und benachrichtigt den Interviewer mit Link und Kandidaten-Zusammenfassung.", "trigger": { "typ": "Kalender-Integration, kein Zeitplan und kein Webhook", "bedingung": "Der Workflow startet, sobald im verbundenen Kalender-Tool ein neues Ereignis angelegt wird, dessen Titel auf die konfigurierte Suchanfrage passt, im Standardfall das Präfix \"Interview:\". Die Terminbeschreibung muss die Zeilen \"Candidate ID: [ID]\" und \"Job ID: [ID]\" im exakten Textformat enthalten, der Interviewer steht in der Teilnehmerliste." }, "schritte": [ { "nr": 1, "titel": "Trigger: neuer Interview-Termin", "rolle": "mensch", "aktion": "Ein Kalendereintrag mit dem Titel-Präfix \"Interview:\" (Suchanfrage konfigurierbar) wird im verbundenen Kalender-Tool angelegt. Die Terminbeschreibung enthält Text im Format \"Candidate ID: [ID]\" und \"Job ID: [ID]\", die Teilnehmerliste enthält den Interviewer.", "prompt_ref": null, "eingang": [], "ausgang": [ "Termin-Titel", "Termin-Beschreibung (Rohtext)", "Teilnehmerliste", "Termin-Datum" ] }, { "nr": 2, "titel": "Kandidat und Stelle laden", "rolle": "automatisch", "aktion": "Ein Code-Schritt liest per Textmuster (regulärer Ausdruck) aus der Terminbeschreibung Kandidaten-ID, Job-ID, Interviewer-Adresse, Termin-Titel und Termin-Datum aus. Mit Kandidaten-ID und Job-ID werden anschließend zwei ATS-Abrufe parallel ausgeführt, damit sich die Wartezeit nicht addiert: der eine lädt das Kandidatenprofil (Name, Berufserfahrung, Qualifikationen), der andere die Stellenbeschreibung (Titel, Abteilung, Anforderungen). Schlägt einer der beiden Abrufe fehl, bricht der Lauf ab.", "prompt_ref": null, "eingang": [ "Termin-Beschreibung (Rohtext)", "Teilnehmerliste" ], "ausgang": [ "Kandidatenprofil", "Stellenbeschreibung", "Interviewer-Adresse", "Termin-Datum" ] }, { "nr": 3, "titel": "Fragenkatalog generieren", "rolle": "automatisch", "aktion": "Ein KI-Agent im Erstellungsmodus wartet, bis Kandidatenprofil und Stellenbeschreibung aus beiden parallelen Abrufen vorliegen, und erzeugt daraus eine strukturierte Ausgabe mit zwei Feldern: questions_catalog, der vollständige Fragenkatalog mit 12 bis 15 Fragen in drei Kategorien, und success, ein Boolescher Wert, der anzeigt, ob die Erstellung geglückt ist.", "prompt_ref": "interview-fragen-generator", "eingang": [ "Kandidatenprofil", "Stellenbeschreibung", "Termin-Datum" ], "ausgang": [ "Fragenkatalog (Feld questions_catalog)", "Erfolgsstatus (Feld success)" ] }, { "nr": 4, "titel": "Im Notiz-Tool speichern", "rolle": "automatisch", "aktion": "Der Inhalt der neuen Seite wird direkt aus dem Feld questions_catalog befüllt. Ein eigener KI-Schritt formuliert den Seitentitel aus Kandidat, Position und Termin-Datum. Die Seite wird standardmäßig im persönlichen Workspace des Notiz-Tools angelegt, der Ablageort (parentId, parentType) und die Icon-Kennzeichnung der Seite sind umstellbar.", "prompt_ref": null, "eingang": [ "Fragenkatalog (Feld questions_catalog)", "Kandidatenprofil", "Stellenbeschreibung", "Termin-Datum" ], "ausgang": [ "Link zur abgelegten Seite" ] }, { "nr": 5, "titel": "Interviewer benachrichtigen", "rolle": "ergebnis", "aktion": "Betreff und Text der E-Mail werden von zwei eigenen KI-Schritten formuliert: der Betreff aus Kandidat und Termin-Datum, der Text im HTML-Format aus Termin-Datum, Kandidatenprofil und dem Link zur Notiz-Seite. Empfänger ist die Interviewer-Adresse aus der Extraktion in Schritt 2.", "prompt_ref": null, "eingang": [ "Link zur abgelegten Seite", "Interviewer-Adresse", "Kandidatenprofil", "Termin-Datum" ], "ausgang": [ "Benachrichtigung an Interviewer" ] } ], "prompts": { "interview-fragen-generator": { "titel": "Interview-Fragen-Generator", "text": "Sie sind ein erfahrener HR-Experte und sollen einen personalisierten Interview-Fragenkatalog erstellen.\n\n**Kandidaten-Informationen:**\n- Name: [KANDIDAT_NAME]\n- Position: [POSITION]\n- Erfahrung: [BERUFSERFAHRUNG]\n- Besondere Qualifikationen: [QUALIFIKATIONEN]\n\n**Stellenbeschreibung:**\n[STELLENBESCHREIBUNG]\n\n**Aufgabe:**\nErstellen Sie einen strukturierten Interview-Fragenkatalog mit 12 bis 15 Fragen, unterteilt in folgende Kategorien:\n\n1. **Fachliche Kompetenz** (5 bis 6 Fragen): Fragen zu technischen Skills und Erfahrungen, die spezifisch auf die Stellenanforderungen und den Lebenslauf des Kandidaten zugeschnitten sind.\n\n2. **Soft Skills und Arbeitsweise** (4 bis 5 Fragen): Verhaltensbasierte Fragen zu Teamarbeit, Kommunikation und Problemlösung.\n\n3. **Cultural Fit und Motivation** (3 bis 4 Fragen): Fragen zu Werten, Arbeitskultur-Präferenzen und Motivation für die Position.\n\n**Format:**\n- Jede Frage mit kurzer Begründung, warum sie relevant ist.\n- Markieren Sie die Priorisierung der fünf wichtigsten Fragen.\n- Ergänzen Sie Hinweise auf mögliche Red Flags in den Antworten." } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Termin-Beschreibung (Rohtext mit Kandidaten-ID und Job-ID), Teilnehmerliste, Termin-Datum" }, { "von": 2, "nach": 3, "nutzlast": "Kandidatenprofil aus dem ersten ATS-Abruf und Stellenbeschreibung aus dem zweiten, parallel laufenden ATS-Abruf" }, { "von": 3, "nach": 4, "nutzlast": "Strukturierte Agenten-Ausgabe mit den Feldern questions_catalog und success" }, { "von": 4, "nach": 5, "nutzlast": "Link zur abgelegten Notiz-Seite" }, { "von": 2, "nach": 5, "nutzlast": "Interviewer-Adresse, aus der Terminbeschreibung beziehungsweise Teilnehmerliste extrahiert" } ], "voraussetzungen": [ "Kalender-Tool als Trigger (Google, Outlook oder Calendly), mit Kandidaten-ID und Job-ID im Format \"Candidate ID: [ID]\" und \"Job ID: [ID]\" in der Terminbeschreibung", "Recruiting-Tool oder ATS für Profil und Stellenbeschreibung (Personio, Greenhouse, Lever oder ähnlich)", "Notiz-Tool für den Fragenkatalog (Notion, Evernote, OneNote oder ähnlich), mit Schreibzugriff auf den gewählten Ablageort", "LLM-Zugang per API-Key (OpenAI, Claude oder Gemini) für den Agenten-Schritt und die Textbausteine", "E-Mail-Versand für die Benachrichtigung (Gmail, Outlook oder ähnlich)" ], "fehlerbehandlung": [ { "fall": "Allgemeine Fehlerstrategie", "massnahme": "Jeder Schritt ist auf Abbruch bei Fehler eingestellt. Schlägt ein ATS-Abruf, der KI-Agent, die Ablage im Notiz-Tool oder der Mail-Versand fehl, stoppt der gesamte Lauf, ohne automatischen Wiederholungsversuch." }, { "fall": "Kandidaten-ID fehlt im Termin oder folgt nicht dem erwarteten Textmuster", "massnahme": "Ein Pflichtfeld oder eine feste Vorlage im Recruiting-Tool sowie eine verbindliche Formatkonvention in der Terminbeschreibung schaffen Abhilfe." }, { "fall": "Job-ID fehlt oder ist nicht mit dem Kandidaten verknüpft", "massnahme": "Das ATS-Mapping prüfen. Ohne Stellenbeschreibung keinen generischen Katalog erzeugen, sondern den Fall an das Recruiting-Team eskalieren." }, { "fall": "Interviewer-Adresse wird nicht korrekt aus der Teilnehmerliste extrahiert", "massnahme": "Das Textmuster beziehungsweise den Domain-Filter im Extraktionsschritt anpassen, bei Panel-Interviews alle internen Teilnehmenden benachrichtigen." }, { "fall": "Ablage im Notiz-Tool schlägt fehl", "massnahme": "Schreibrechte, Ablageort (parentId, parentType) und das verwendete Template prüfen." }, { "fall": "Regex-Muster in der Extraktion passt nicht zum eigenen Kalender-Format", "massnahme": "Das Textmuster für Kandidaten-ID und Job-ID an die tatsächliche Formatierung der Terminbeschreibung anpassen, Standardformat ist \"Candidate ID: [ID]\" und \"Job ID: [ID]\"." } ], "platzhalter": [ { "name": "KALENDER_SUCHFILTER", "quelle": "Suchanfrage im Trigger-Knoten, im Standardfall das Titel-Präfix \"Interview:\", legt fest, welche Termine den Lauf starten" }, { "name": "candidateId", "quelle": "Per Textmuster aus der Terminbeschreibung extrahiert (\"Candidate ID: [ID]\"), speist das Feld id im ersten ATS-Abruf" }, { "name": "jobId", "quelle": "Per Textmuster aus der Terminbeschreibung extrahiert (\"Job ID: [ID]\"), speist das Feld id im zweiten ATS-Abruf" }, { "name": "interviewerEmail", "quelle": "Aus der Teilnehmerliste des Termins extrahiert, speist das Feld mailRecipient der Benachrichtigung" }, { "name": "eventDate", "quelle": "Termin-Datum aus dem Kalender-Event, fließt in Betreff und Text der Benachrichtigung sowie in den Titel der Notiz-Seite ein" }, { "name": "ATS_ZUGANG", "quelle": "Verbindung zum Recruiting-Tool, über die candidateId und jobId aufgelöst werden" }, { "name": "parentId / parentType", "quelle": "Ablageort der neuen Seite im Notiz-Tool, Standard ist der persönliche Workspace (createInPersonalRoot), umstellbar auf eine feste Datenbank oder Seite" }, { "name": "LLM_ZUGANG", "quelle": "Zugang zum KI-Modell, das den Fragenkatalog im Agenten-Schritt und die Textbausteine für Titel, Betreff und Mailtext erzeugt" }, { "name": "INTERNE_MAIL_DOMAIN", "quelle": "Filterkriterium im Extraktionsschritt, nach dem die Teilnehmerliste auf interne Interviewer eingegrenzt wird" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "mic", "recommended": [ { "slug": "einarbeitungs-spur", "category": "workflow", "name": "The Onboarding Track", "teaser": "A workflow that automatically creates a position specific onboarding checklist for the first 30, 60 and 90 days when a new employee is added to the HR system, generates tasks from it in the project tool, and notifies the manager and IT in good time.", "domaene": "Menschen & Organisation", "itemIcon": "graduation-cap" }, { "slug": "change-briefing", "category": "skill", "name": "The Change Briefing", "teaser": "Builds a complete communication plan for change projects from audiences, core messages and timeline, including a cascade and honest FAQ.", "domaene": "Menschen & Organisation", "itemIcon": "refresh-cw" }, { "slug": "workshop-drehbuch", "category": "skill", "name": "The Workshop Playbook", "teaser": "Turns a workshop's topic, audience, duration and learning objectives into a complete, ready-to-run training playbook with schedule, exercises, handout and feedback form.", "domaene": "Menschen & Organisation", "itemIcon": "users-round" }, { "slug": "workshop-architekt", "category": "assistent", "name": "The Workshop Architect", "teaser": "Guides you interactively from goal definition to a finished, fully timed workshop agenda with detailed exercises, ready for groups from 5 to 25 or more, in person, online or hybrid.", "domaene": "Menschen & Organisation", "itemIcon": "users-round" }, { "slug": "onboarding-strecke", "category": "workflow", "name": "The Onboarding Pipeline", "teaser": "Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "door-open" }, { "slug": "ankuendigungs-briefing", "category": "skill", "name": "The Announcement Briefing", "teaser": "Produces internal communication texts for companies, from announcements to change communication, adapting tone and depth to how sensitive the topic is.", "domaene": "Menschen & Organisation", "itemIcon": "megaphone" }, { "slug": "feedback-muster", "category": "skill", "name": "The Feedback Framework", "teaser": "The Feedback Framework turns an observation into feedback using established methods such as SBI, feedforward or radical candor, complete with phrasing variants and a full conversation guide.", "domaene": "Menschen & Organisation", "itemIcon": "message-square-quote" }, { "slug": "schulungs-architekt", "category": "assistent", "name": "The Training Architect", "teaser": "The Training Architect turns raw subject-matter expertise into a ready-to-use, two-hour training module complete with learning objectives, exercises and knowledge checks.", "domaene": "Menschen & Organisation", "itemIcon": "graduation-cap" }, { "slug": "stakeholder-navigator", "category": "assistent", "name": "The Stakeholder Navigator", "teaser": "Creates structured communication plans with target audiences, core messages, suitable channels and a clear timeline for coordinated stakeholder communication around projects, changes or campaigns.", "domaene": "Menschen & Organisation", "itemIcon": "users" }, { "slug": "artisan", "category": "tool", "name": "Artisan", "teaser": "Artisan is an AI outbound sales tool centered on Ava, an autonomous agent that researches leads, personalizes email sequences and manages follow-ups for B2B SaaS teams.", "domaene": "Vertrieb & Outreach", "logoFile": "artisan.png", "logoEinzug": 0.78 } ] }