Integration
Connect Splitwise to MedlinePlus Genetics
When something happens in Splitwise, your agent does the next thing in MedlinePlus Genetics. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Splitwise and MedlinePlus Genetics to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Splitwise and MedlinePlus Genetics
Triggers and actions 1 trigger ยท 4 actions
Trigger
New ExpenseTriggers when a new expense is created. Optionally, filter for a specific group.
Action
Create ExpenseCreates a new expense, optionally in a group or with a specific set of friends.
Action
Find genetics contentSearch MedlinePlus Genetics (db=ghr) by keyword term. GET https://wsearch.nlm.nih.gov/ws/query?db=ghr&term={term}&retmax={n}. Returns ranked XML list of matching genetic condition/gene/chromosome pages with titles, URLs, and snippets. Supports retmax (default 10) for result count.
Action
Get genetic condition detailsFetch full detail for one MedlinePlus Genetics page (genetic condition, gene, chromosome, or mtDNA) by its page slug. GET https://medlineplus.gov/download/genetics/condition/{slug}.json (or gene/chromosome/mtdna path per the page's category). Returns summary, synonyms, inheritance pattern, related conditions, and db-key cross-references.
Action
List genetics topicsRetrieve the full index of MedlinePlus Genetics topics. GET https://medlineplus.gov/download/TopicIndex.xml. Returns titles, URLs, and synonyms for every Help Me Understand Genetics page plus every genetic condition/gene/chromosome/mtDNA page on the site.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.