Integration
Connect Mailparser to CSR.plus
When something happens in Mailparser, your agent does the next thing in CSR.plus. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and CSR.plus 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 Mailparser and CSR.plus
Triggers and actions 2 triggers · 8 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
- New Email Parsed (One Request Per Row)
Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
Action
Check SSLfull SSL/TLS check for a host: A-F grade, TLS protocol/cipher probes, and HSTS status.
- Decode CSR
parse a PEM-encoded CSR and return its subject fields, SANs, and public key details.
- Find certificate transparency logs
search Certificate Transparency logs for a given domain.
- Generate CSR
generate a certificate signing request and matching private key (RSA or ECDSA). Body: common_name, sans[], organization, organizational_unit, locality, state, country, key_type, key_size, passphrase (all except common_name optional). Returns PEM-encoded CSR and private key.
- Get CAA records
retrieve CAA records and related DNS details (A, AAAA, NS, MX) for a domain.
- Get OpenSSL trace
return raw openssl s_client output for a domain.
- Get revocation status
check CRL/OCSP revocation status of the certificate currently served by a domain.
- Trace SSL handshake
step-by-step TLS handshake trace for a given host and port.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.