
Step 1: Connect your stack
27+ native integrations plus 9,800+ tools via managed connectors. Mostly one-click OAuth, a few API keys. No webhooks, no Zapier zaps.
Viktor works in Amplitude for you. Ask in Slack or Microsoft Teams.
Viktor is an AI employee that connects to Amplitude and helps you track product usage and feature adoption, running 11 Amplitude actions for you like List Cohorts, Search Users, and Create Cohort. Ask in plain English from your workspace; Viktor does the work in Amplitude and reports back. Viktor connects with a scoped API key.
Viktor connects to your Amplitude account and completes work in it. He doesn't just answer questions about Amplitude, he takes the actions on your behalf and delivers the finished result to your workspace.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Amplitude actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs.
About Amplitude
Build better products by turning your user data into meaningful insights, using Amplitude's digital analytics platform and experimentation tools.
Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Amplitude, does the work and posts the result in the same thread, so nobody has to switch tabs.
He can also run Amplitude work on a schedule, like a weekly Amplitude summary posted to your team's channel. Anything sensitive waits for your approval before it runs.
You ask in your workspace
Describe what you need in plain English
Viktor picks the actions
Selects from 11 Amplitude actions, chains them together
Runs in Amplitude
Helps you track product usage and feature adoption - your real data.
Reports back
Delivers the finished result to your workspace
Messages you'd actually send. Paste one into your workspace, swap in your specifics, and Viktor takes it from there.
“Pull this week's activation funnel from Amplitude and flag the biggest drop-off.”
— you, to @Viktor
“Investigate why a key metric dropped in Amplitude last week and report what you find.”
— you, to @Viktor
“Build a report on the new feature's adoption in Amplitude and post it every Monday.”
— you, to @Viktor
“Watch Amplitude for a spike in a key metric and alert me with context.”
— you, to @Viktor

27+ native integrations plus 9,800+ tools via managed connectors. Mostly one-click OAuth, a few API keys. No webhooks, no Zapier zaps.
Message Viktor like a teammate: "Pull this week's MRR from Stripe." "Triage new Linear bugs." "Pause Meta ads over $40 CPA." Any tool.
Viktor opens the tools, runs the work, and posts back exactly what changed. Sensitive actions wait for your approval. It’s all logged.
Ask in plain English from your workspace. Viktor picks the right Amplitude actions, runs the work, and reports back. No workflows to build.
Create a static cohort in Amplitude from an explicit list of user or Amplitude IDs via POST /api/3/cohorts/upload (the only REST-documented cohort creation endpoint; behavioral/dynamic cohorts cannot be created via REST). Use List Cohorts to find an existing cohort ID if updating.
Download a completed cohort export's member list (step 3 of 3: request -> status -> download). Call Request Cohort Download then Get Cohort Download Status first, and only call this once status is JOB COMPLETED — calling it earlier will fail. Returns one record per member (amplitudeid/userid, plus any requested user properties) — not the cohort's own metadata (name, size, definition); use List Cohorts for that.
Check whether a cohort download job has finished (step 2 of 3: request -> status -> download). Call Request Cohort Download first to get a requestId. This action polls internally for up to ~35 seconds before returning, since Amplitude's export jobs commonly take 30-60+ seconds regardless of cohort size. If the returned asyncstatus is still JOB INPROGRESS, call this action again with the same request ID (it may take a few calls) — do not call Download Cohort File until asyncstatus is JOB COMPLETED.
Query event segmentation data (counts, uniques, and other metrics) for one or more events over a date range from the Amplitude Dashboard REST API. Use this to analyze how an event trends over time, optionally broken down by user properties.
Compute conversion rates across an ordered (or unordered/sequential) set of funnel steps over a date range from the Amplitude Dashboard REST API. Provide one event definition per funnel step.
Compute retention (return rate) between a start event and a return event over a date range from the Amplitude Dashboard REST API.
Fetch the event stream for a single user by their numeric Amplitude ID from the Amplitude Dashboard REST API. Each returned event defaults to just ; pass \fields\ to also get e.g. \eventproperties\, \userproperties\, \uuid\, \sessionid\, \amplitudeid\, \deviceid\ (event objects can carry many properties, so these stay opt-in). Amplitude's API caps each request at events with no cursor; this tool pages \offset\ forward automatically to collect up to \limit\ events (set it above , up to , to fetch more than one page). Use Search Users first to resolve the Amplitude ID.
List all behavioral cohorts in the Amplitude project. Returns a \cohorts\ array; each entry defaults to . Pass \fields\ to get more, e.g. \description\, \published\, \archived\, or the large \definition\ (the cohort's filter logic) / \owners\/\viewers\ (email arrays). Use this to discover valid cohort IDs for Request Cohort Download (step 1 of 3, followed by Get Cohort Download Status and Download Cohort File, to fetch a cohort's member list).
Start a behavioral cohort download job (step 1 of 3: request -> status -> download, per Amplitude's Behavioral Cohorts Download API). Returns a requestid — pass it to Get Cohort Download Status to poll until the job completes, then to Download Cohort File to fetch the member list. Use List Cohorts first to discover valid cohort IDs.
Ask for outcomes that span tools - Viktor pulls from Amplitude, cross-references the rest of your stack, and delivers one finished result.
Yes. Amplitude is one of the 9,800+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Amplitude from their workspace - no workflow builder, no code.
Ask Viktor in your workspace to connect Amplitude, then paste an API key from your Amplitude account when prompted. Viktor stores the key securely, uses only the scopes you grant, and you can revoke it at any time. Setup takes about two minutes.
Viktor can run 11 Amplitude actions, including List Cohorts, Search Users, and Create Cohort - and chain them with other tools in a single request. In practice that means Viktor helps you track product usage and feature adoption. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done.
No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which Amplitude actions to take, runs them, and reports back.
Start free. Viktor delivers.
Start for free today. No credit card required.