Integration
Connect PhishStats to Amplitude
When something happens in PhishStats, your agent does the next thing in Amplitude. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PhishStats and Amplitude 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 PhishStats and Amplitude
Triggers and actions 1 trigger · 13 actions
Trigger
New phishing recordPolling trigger for newly added phishing URLs. GET https://api.phishstats.info/api/phishing?_sort=-date&_p=1&_size=100 (optionally filtered by _where=(countrycode|tld|asn,eq,value) etc.) — the database refreshes every ~90 minutes; poll no more often than that. Dedup/order by the id or date field (descending). Auth via X-API-Key header (psk_...) or ?apikey=psk_...; anonymous allowed at a lower quota.
Action
Find phishing recordsSearch the PhishStats phishing database. GET https://api.phishstats.info/api/phishing with _where=(field,operator,value) filters (eq/ne/gt/lt/like, combined with ~and/~or) over fields like url, ip, asn, countrycode, tld, title, score, date, id; _sort=field (-field for desc); _p=page (default 1), _size=records per page (default 20, max 100). Auth via X-API-Key header (psk_...), Authorization: Bearer psk_..., or ?apikey=psk_... query param; anonymous is allowed at a lower quota.
Action
Batch upload eventsSends 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.
Action
Export event dataExports every event Amplitude recorded in a time window, as a zip archive of event data.
Action
Get cohortReturns one behavioral cohort's details, including its name, size and when it was last recalculated.
Action
Get event segmentationCounts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
Action
Get funnel analysisRuns a funnel over a series of events and returns how many users reached each step and how many dropped off.
Action
Get retention analysisShows how many users came back and did something again after a starting event, over a date range.
Action
Get user propertiesLooks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
Action
Group identifySets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
Action
Identify userSets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
Action
List cohortsLists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
Action
Send eventRecords a single event in Amplitude for a user, with optional event and user properties.
Action
Upload cohortCreates 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.