Integration
Connect Paperform to PhishStats
When something happens in Paperform, 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 Paperform 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 Paperform and PhishStats
Triggers and actions 4 triggers · 3 actions
Trigger
New Form SubmissionTriggers when a new submission is received for a form.
Trigger
New Papersign Document CompletedFires when a Papersign document is fully signed by all participants. Webhook-delivered via Papersign Webhooks event subscription.
Trigger
New Partial Form SubmissionTriggers when a new partial submission is received for a form.
Action
Create SpaceCreates a Papersign space to organise documents, and optionally opens it to your team.
Action
Update SpaceRenames a Paperform space.
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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.