Integration
Connect Mailparser to Minor Planet Center
When something happens in Mailparser, your agent does the next thing in Minor Planet Center. 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 Minor Planet Center 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 Minor Planet Center
Triggers and actions 2 triggers · 11 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
Find MPECsSearch Minor Planet Electronic Circulars by object or search terms, optionally filtered by issue date range (data.minorplanetcenter.net/api/mpecs).
- Find near-duplicate observations
Search the MPC's published observation database for near-duplicates of a given observation by time and angular proximity (data.minorplanetcenter.net/api/cnd).
- Get action code
Resend an observation submission's action code (used to retract observations or label objects) to the email address on file (data.minorplanetcenter.net/api/action-codes/retrieve).
- Get magnitude band
Retrieve reference information for a magnitude band used in MPC observations, or all bands (data.minorplanetcenter.net/api/mag-band).
- Get NEOCP observations
Retrieve observation data for an object currently on the Near-Earth Object Confirmation Page by tracklet identifier (data.minorplanetcenter.net/api/get-obs-neocp).
- Get object identifier
Look up the designations and identification details for a minor planet or comet given a name, provisional or permanent designation (data.minorplanetcenter.net/api/query-identifier).
- Get observations
Retrieve recorded astrometric observation data for a solar system object by designation (data.minorplanetcenter.net/api/get-obs).
- Get observation status
Check the processing status of individual submitted observations by tracklet/station, observation ID, obs80 string, or submission block ID (WAMO — data.minorplanetcenter.net/api/wamo).
- Get observatory codes
Retrieve details for one or all observatories registered with the MPC by observatory code (data.minorplanetcenter.net/api/obscodes).
- Get orbital elements
Retrieve orbital elements and related parameters for a solar system object by designation (data.minorplanetcenter.net/api/get-orb).
- List objects
List solar system objects belonging to a named group such as NEOs, comets, or TNOs, ordered by designation (data.minorplanetcenter.net/api/list).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews