Integration
Connect Mailparser to Harness.io
When something happens in Mailparser, your agent does the next thing in Harness.io. 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 Harness.io 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 Harness.io
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
Add ConnectorCreate a new connector (e.g. GitHub, Kubernetes, Docker registry). POST /ng/api/connectors
- Add Environment
Create a new deployment environment in a project. POST /ng/api/environmentsV2
- Add Secret
Create a new secret (text/file/SSH key) in a scope. POST /ng/api/v2/secrets
- Create Project
Creates a new project in Harness.
- Execute Pipeline
Trigger a pipeline execution. POST /pipeline/api/pipeline/execute/{pipelineIdentifier}
- Get Pipeline
Fetch a single pipeline definition by identifier. GET /pipeline/api/pipelines/{pipelineIdentifier}
- Get Pipeline Execution
Fetch a pipeline execution's status and details by execution id. GET /pipeline/api/pipelines/execution/{planExecutionId}
- Get Project
Fetch a single project by identifier. GET /ng/api/projects/{identifier}
- List Pipeline Executions
List pipeline executions for a project. POST /pipeline/api/pipelines/execution/summary
- List Pipelines
List pipelines for a project. POST /pipeline/api/pipelines/list
- List Projects
List projects in the account/org. GET /ng/api/projects
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.