--- title: "ChytryStart Integration" description: "Turn a Czech name into the grammatical forms needed to address someone properly, including vocative case and gender detection. Agents personalize Czech-language messages without getting the grammar wrong." url: https://flowrunner.ai/integrations/chytrystart date_modified: 2026-08-07T17:20:23-07:00 --- # ChytryStart [Utilities & Personal](https://flowrunner.ai/integrations/category/utilities-personal) Turn a Czech name into the grammatical forms needed to address someone properly, including vocative case and gender detection. Agents personalize Czech-language messages without getting the grammar wrong. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 2 actions · API key · available [ChytryStart website](https://chytrystart.cz/) · [Platform Documentation](https://www.chytrystart.cz) · Capability data verified 2026-08-04 1. Nightly sync pulls newly created Czech contacts into the campaign audience 2. Agent reads the single full-name field, academic titles and all 3. Agent calls Analyze Full Name and receives the split name parts, the vocative forms and the detected gender 4. Agent compares the detected gender against the salutation word already stored on the contact record 5. Agent isolates rows where gender came back undetermined or disagrees with the stored value 6. Agent posts the isolated rows to the campaign owner with the source name and both candidate salutations 7. A Czech-speaking owner confirms the salutation for those rows before the send is released ## What This Integration Enables Most contact databases were designed by people writing in English, where a name is a string you drop into a merge field and the greeting still reads normally. Czech does not work that way. Direct address takes the vocative, the fifth of seven grammatical cases, and the salutation word in front of the name carries grammatical gender. A merge field that emits the nominative produces a greeting that a Czech reader identifies as machine-generated in the first two words, and sometimes reads as curt. ChytryStart is the [connector](https://flowrunner.ai/concepts/connectors) for teams who found that out from a reply rather than from a review. The scope is deliberately narrow and worth understanding before you pick it. ChytryStart answers the greeting question: it takes a first name, or a full name string with academic titles attached, and returns the vocative forms, the detected gender, ready-made salutation combinations in both abbreviated and fully spelled-out variants, and the Czech and Slovak name-day dates for that first name. It does not inflect a name into the genitive or the dative, so a contract clause that needs "to Petr Novak" in the dative is a different job. What it does cover is the case that shows up in almost every outbound message, plus the two enrichment fields that most Czech contact records are missing. ### Without FlowRunner **Nominative greetings**: Czech recipients are addressed with the dictionary form of their own name **Titles inside the first name**: An imported "Ing. Petr" lands in the first-name field and shows up in the greeting **Gender decided by eye**: Someone scans the list and picks between the male and female salutation by hand ### With FlowRunner **Vocative by default**: Every greeting uses the case Czech requires when you address a person directly **Separated name parts**: Titles, first name and surname are split before the record is written **Gender from the name**: The salutation word follows the detected gender, and the unclear rows are surfaced rather than guessed ## Use Case Scenarios ### Cleaning an imported list before the first send A marketing team imports several thousand Czech contacts from an event registration into [HubSpot](https://flowrunner.ai/integrations/hubspot). The registration form collected one free-text name field, so the data arrives as strings like "MUDr. Jana Svobodova" with the title fused to the name. An agent runs Analyze Full Name across the import, writes the separated first name, surname and titles back to their own properties, stores the vocative forms on the record, and populates the gender field that segmentation later depends on. The list stops being a pile of strings and becomes a set of records the campaign tooling can address correctly. ### Name-day greetings that land on the right day Name days matter in Czech and Slovak social convention in a way that has no direct English equivalent, and the date depends on the first name rather than on anything stored in the CRM. A scheduled agent runs Analyze Name Parts across the active customer base, reads back the Czech and Slovak name-day dates, and builds a calendar of who to greet and when. On the morning of each date the agent assembles the message using the vocative form already on the record and queues it in [Brevo](https://flowrunner.ai/integrations/brevo). The greeting arrives on the correct day, in the correct case, without anyone maintaining a lookup table. ### Generated documents that carry the person's title A training provider issues completion certificates from a template. An agent reads the attendee record, calls Analyze Full Name to separate the academic title from the name, and passes both to [APITemplate](https://flowrunner.ai/integrations/apitemplate) so the certificate prints the title in front of the name where Czech convention expects it. Where the title split is ambiguous, for example an unusual abbreviation the service did not recognize, the agent does not print its best guess. It holds that certificate out of the batch and asks the program coordinator to confirm the rendering before the run is released. ## Human-in-Loop Highlight Gender detection is the load-bearing field here, because the Czech salutation word in front of the name is gendered and appears before anything else in the message. For most Czech first names ChytryStart resolves it cleanly. For a unisex name, or a foreign first name carried by a Czech resident, the detection can come back undetermined or can disagree with what the CRM already holds, and there is no way to recover a mis-gendered greeting once the campaign is sent. So the agent does not pick. It collects every row where the detection is undetermined or contradicts the stored value, posts them to the campaign owner in [Slack](https://flowrunner.ai/integrations/slack) as a short list, and asks: "These 14 contacts came back without a confident gender. Here is the name as imported and both candidate salutations for each. Which one goes out, or should they be dropped from this send?" The rest of the audience proceeds on schedule. Only the [automation exceptions](https://flowrunner.ai/concepts/automation-exceptions) wait, which is what [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) is for: the agent handles the volume and hands back the judgment calls it cannot make honestly. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 2 actions ### Name Analysis 2 - **Analyze Name Parts** Takes a Czech first name, optionally with a surname, and returns the vocative forms used to address the person directly, the detected gender, and the Czech and Slovak name-day dates for that first name. It also returns ready-made salutation combinations pairing the vocative gender word with the name, in an abbreviated and a fully spelled-out variant. Use this when your contact data already keeps first name and surname in separate fields, which is the normal case for records created through a structured form. - **Analyze Full Name** Takes a complete name as a single string, including any academic titles, and splits it into its parts. It returns the separated first name and surname, the full name with and without titles, the vocative forms, the detected gender, the Czech and Slovak name-day dates, and the same abbreviated and fully spelled-out salutation combinations. Use this when the name arrived in one field, which is what happens with event registrations, free-text signup forms and most spreadsheet imports. ## Frequently Asked Questions ### What can FlowRunner do with ChytryStart? FlowRunner agents can run Analyze Name Parts and Analyze Full Name in ChytryStart. ### Does connecting ChytryStart to FlowRunner require OAuth? No. ChytryStart connects to FlowRunner with an API key, no OAuth flow required. ### Can ChytryStart trigger a FlowRunner workflow automatically? ChytryStart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at ChytryStart?** This integration exposes ChytryStart to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/chytrystart. Site index: https://flowrunner.ai/llms.txt