FlowRunner
PricingContact
Theme
Start Free

Sklonovani jmen

Utilities & Personal

Inflect Czech and foreign personal names into any of the seven Czech grammatical cases and detect the gender behind a name. Agents address Czech recipients correctly instead of defaulting to the nominative.

4 actions API key available
A document run is queued for a batch of Czech-language contracts
Agent calls Get Account Credit and compares the remaining balance against the number of names in the run
Agent calls Decline Name once per recipient, requesting the case each template slot needs
Agent confirms each name came back inflected rather than echoed back unchanged
Agent separates the rows the service cannot answer fully, including company names outside the vocative
Agent posts those rows to the legal operations owner with the template slot and the case required
A Czech-speaking reviewer supplies or confirms the wording before any document is generated

What This Integration Enables

Czech has seven grammatical cases, and a personal name changes shape in every one of them. The greeting takes the vocative. "Delivered to Petr Novak" takes the accusative or the dative depending on the verb. "Petr Novak's order" is not a possessive built with an apostrophe but a derived adjective that agrees with the noun it modifies. A document template written by an English-speaking developer has one name field and no concept of any of this, which is why generated Czech contracts, invoices and delivery notes so often read as though nobody proofed them. Sklonovani jmen exists because the fix is grammatical, not editorial.

The service inflects Czech and foreign personal names into any of the seven cases, accepts names written in Latin script or Ukrainian Cyrillic, handles academic titles and military ranks, and lets you control exactly which parts appear in the output and whether a salutation is prefixed. It also detects the gender behind a name without inflecting it, and builds Czech possessive adjectives. Two things are worth knowing before you design a flow around it: work is metered, with each processed name consuming one credit and Get Account Credit available free of charge to check the balance first, and the possessive endpoint is a vendor-declared beta. Both facts shape where an agent should stop and ask.

Without FlowRunner

One form used everywhere The same nominative spelling is pasted into the greeting, the address block and the possessive phrase
Foreign names skipped Names outside the Czech pattern are left alone, so part of the batch reads correctly and part does not
Runs fail quietly A batch stops partway and nobody can tell which documents came out with the wrong form

With FlowRunner

Case chosen per slot Each slot in the template receives the case that slot actually requires
Foreign and Cyrillic names covered Latin-script and Ukrainian Cyrillic names go through the same call, titles and military ranks included
Run sized before it starts Remaining credit is checked against the row count before the first document is produced

Use Case Scenarios

Contracts generated from CRM records

A services firm generates Czech-language engagement letters from deal records in Pipedrive. The template needs the counterparty's name in three different shapes: the vocative in the opening address, the dative in the clause describing who the obligations fall to, and the nominative in the signature block. An agent reads the deal, calls Decline Name three times with the case each slot needs, fills the template, and routes the finished document to DocuSign for signature. The same record produces three different spellings of the same name, which is exactly what the language requires and exactly what a merge field cannot do.

Onboarding documents for Ukrainian-Cyrillic names

A Czech employer hiring Ukrainian staff has names arriving in Cyrillic from identity documents and in transliterated Latin script from the recruiting system. An agent normalizes both through Decline Name, which accepts either script, and uses Detect Gender to fill the gender field the payroll export requires and the HR record often lacks. The resulting onboarding pack addresses each new hire correctly in every place their name appears, and the payroll export stops bouncing on empty fields. Where Detect Gender returns undetermined, the record is held for the people operations owner rather than defaulted.

Bulk list normalization with a spend guard

Before a large mailing, an agent needs to inflect several thousand names held in Google Sheets. Each name costs a credit, and a run that exhausts the balance halfway leaves a list where some rows are correctly inflected and some are still nominative, with nothing in the data marking which is which. So the agent calls Get Account Credit first, compares the balance and the remaining free daily allowance against the row count, and refuses to start a run it cannot finish. If the balance is short, it reports the shortfall and the exact number of rows it can safely process instead of beginning and stopping.

Human-in-Loop Highlight

The gate here sits on a limit the vendor states plainly: company names are supported in the vocative case only. That is a narrow-sounding restriction with a wide consequence, because a B2B invoice or contract regularly needs the counterparty in the genitive or the dative, and the counterparty is a company rather than a person. Ask the service for it and you get either nothing usable or something that will pass a spellcheck and fail a lawyer. The same caution applies to Get Possessive Form, which the vendor labels a beta feature, in a document where a possessive phrase carries legal meaning. So the agent runs the full batch, generates nothing, and stops on those rows first. It posts them to the legal operations owner in Microsoft Teams with the counterparty name, the template slot, and the case the slot requires: "Three of 240 contracts name a company in a case this service does not inflect. Supply the wording for each, or approve rewording the clause so the company name stays in the nominative." Pulling the line on the whole run because of three rows is the point of a digital andon cord, and it is why human-in-the-loop is a step in the flow rather than a review after the fact.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

4 actions

Name Declension

2
  • Decline Name Inflects Czech and foreign personal names into any of the seven Czech grammatical cases, so letters, invoices and emails address people correctly. It accepts full names in Latin script or Ukrainian Cyrillic, including academic titles and military ranks, and lets you control whether first names, surnames, titles and the leading salutation appear in the output. Several names can be converted in a single call, and each name consumes one credit. Company names are supported in the vocative case only.
  • Get Possessive Form Builds the Czech possessive adjective derived from a name, matching the gender, number and animacy of the noun it will modify, which is how you generate a natural phrase for something belonging to a person. This is a beta feature of the API, and salutation settings are ignored for possessive output. Several names can be processed in one call, and each name consumes one credit.

Contact Enrichment

1
  • Detect Gender Determines the grammatical gender behind a Czech or foreign personal name without inflecting it. It returns male, female, or undetermined for unisex and unrecognized names, alongside the raw single-letter marker the API uses. Use it to choose a salutation, to segment a contact list, or to fill a gender field during enrichment. Several names can be checked in one call, and each name consumes one credit.

Account

1
  • Get Account Credit Reports the current state of the account, including how many whole days the prepaid credit stays valid, the remaining prepaid balance, and the remaining free daily credit. Each processed name costs one credit, so an agent should call this before a large batch to confirm the balance covers the job. The call is free and consumes no credit itself, which makes it the right guard step at the top of any bulk flow.

Frequently Asked Questions

What can FlowRunner do with Sklonovani jmen?

FlowRunner agents can run Decline Name, Detect Gender, and Get Possessive Form in Sklonovani jmen, plus 1 more action.

Does connecting Sklonovani jmen to FlowRunner require OAuth?

No. Sklonovani jmen connects to FlowRunner with an API key, no OAuth flow required.

Can Sklonovani jmen trigger a FlowRunner workflow automatically?

Sklonovani jmen doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Sklonovani jmen

$100 in credits. No card required. Connect in minutes.