Integration
Connect Siteleaf to PhishStats
When something happens in Siteleaf, your agent does the next thing in PhishStats. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Siteleaf and PhishStats 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 Siteleaf and PhishStats
Triggers and actions 5 triggers · 18 actions
Trigger
New CollectionTriggered when a new collection is created.
- New Document
Triggered when a new document is created.
- New Page
Triggered when a new page is created.
- New Site
Triggered when a new site is created.
- Add Collection
Create a new collection on a site. POST https://api.siteleaf.com/v2/sites/:site_id/collections
- Create Document
Creates a new document.
- Create Page
Creates a new page.
- Delete Collection
Delete a collection. DELETE https://api.siteleaf.com/v2/sites/:site_id/collections/:path
- Delete Document
Delete a document. DELETE https://api.siteleaf.com/v2/sites/:site_id/collections/:path/documents/:id
- Delete Page
Delete a page. DELETE https://api.siteleaf.com/v2/sites/:site_id/pages/:id
- Get Document
Get a single document by id. GET https://api.siteleaf.com/v2/sites/:site_id/collections/:path/documents/:id
- Get Page
Get a single page by id. GET https://api.siteleaf.com/v2/sites/:site_id/pages/:id
- Get Site
Get a single site by id. GET https://api.siteleaf.com/v2/sites/:site_id
- List Collections
List collections for a site. GET https://api.siteleaf.com/v2/sites/:site_id/collections
- List Documents
List documents in a collection, filterable by search/visibility/extensions. GET https://api.siteleaf.com/v2/sites/:site_id/collections/:path/documents
- List Pages
List pages for a site, filterable by search/visibility/extensions. GET https://api.siteleaf.com/v2/sites/:site_id/pages
- List Sites
List all sites for the authenticated user. GET https://api.siteleaf.com/v2/sites
- Update Collection
Update a collection's title/path/metadata. PUT https://api.siteleaf.com/v2/sites/:site_id/collections/:path
- Update Document
Update an existing document's title/body/tags/categories/metadata. PUT https://api.siteleaf.com/v2/sites/:site_id/collections/:path/documents/:id
- Update Page
Update an existing page's title/body/metadata. PUT https://api.siteleaf.com/v2/sites/:site_id/pages/:id
- Update Site
Update a site's settings. PUT https://api.siteleaf.com/v2/sites/:site_id
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.
- Find phishing records
Search 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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.