Integration
Connect DecisionRules to Amplitude
When New Rules fires in DecisionRules, your agent runs Send event in Amplitude. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want DecisionRules and Amplitude to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What DecisionRules can start in Amplitude
When New Rules in DecisionRules
then Send event in Amplitude
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with DecisionRules and Amplitude
Triggers and actions 1 trigger · 22 actions
- New Rules
Fires once for each new rule or rule flow added to the DecisionRules space.
- Add folder
Create a folder under a node.
- Add rule
Create a rule in a space.
- Add rule version
Create a new version of a rule.
- Add tags to rule
Add tags to a rule.
- Delete rule
Delete a rule or rule version.
- Get rule
Gets the latest version of a rule by its ID or alias, regardless of publication status.
- List folders
Get the root folder tree.
- List rules
List rules in a space.
- Update rule
Update a rule version.
- Update rule status
Publish/pending/archive a rule version.
- Batch upload events
Sends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.
- Export event data
Exports every event Amplitude recorded in a time window, as a zip archive of event data.
- Get cohort
Returns one behavioral cohort's details, including its name, size and when it was last recalculated.
- Get event segmentation
Counts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
- Get funnel analysis
Runs a funnel over a series of events and returns how many users reached each step and how many dropped off.
- Get retention analysis
Shows how many users came back and did something again after a starting event, over a date range.
- Get user properties
Looks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
- Group identify
Sets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
- Identify user
Sets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
- List cohorts
Lists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
- Send event
Records a single event in Amplitude for a user, with optional event and user properties.
- Upload cohort
Creates a cohort in Amplitude from a list of users you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from DecisionRules
DecisionRules to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DecisionRules to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DecisionRules to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DecisionRules to Google SheetsGoogle Sheets
DecisionRules to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DecisionRules to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Amplitude
Arxiv to AmplitudeOpen-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...
Attio to AmplitudeAttio is the CRM of the future: data-driven, completely customizable and intuitively collaborative.
Questions
DecisionRules and Amplitude, answered
What can start an automation from DecisionRules?
Any of DecisionRules's 1 trigger in the catalog, including New Rules. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Amplitude when something happens in DecisionRules?
Any of Amplitude's 12 actions, including Send event, Upload cohort, Batch upload events and Export event data. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Amplitude to DecisionRules?
Amplitude has no triggers in the catalog today, so automations start in DecisionRules. If you need the other direction, ask: your agent reads Amplitude's API documentation and adds it.
Do I have to build a connector for DecisionRules or Amplitude?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.