Integration
Connect Docparser to Harness.io
When something happens in Docparser, 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 Docparser 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 Docparser and Harness.io
Triggers and actions 2 triggers ยท 13 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
Trigger
Parsed Table Row AvailableTriggers whenever a new Document is processed and parsed table rows are available.
Action
Fetch Document From URLFetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Upload DocumentUploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Add ConnectorCreate a new connector (e.g. GitHub, Kubernetes, Docker registry). POST /ng/api/connectors
Action
Add EnvironmentCreate a new deployment environment in a project. POST /ng/api/environmentsV2
Action
Add SecretCreate a new secret (text/file/SSH key) in a scope. POST /ng/api/v2/secrets
Action
Create ProjectCreates a new project in Harness.
Action
Execute PipelineTrigger a pipeline execution. POST /pipeline/api/pipeline/execute/{pipelineIdentifier}
Action
Get PipelineFetch a single pipeline definition by identifier. GET /pipeline/api/pipelines/{pipelineIdentifier}
Action
Get Pipeline ExecutionFetch a pipeline execution's status and details by execution id. GET /pipeline/api/pipelines/execution/{planExecutionId}
Action
Get ProjectFetch a single project by identifier. GET /ng/api/projects/{identifier}
Action
List Pipeline ExecutionsList pipeline executions for a project. POST /pipeline/api/pipelines/execution/summary
Action
List PipelinesList pipelines for a project. POST /pipeline/api/pipelines/list
Action
List ProjectsList 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.
Each app on its own
Reviews