Pulse integration

AI & Machine Learning · 1 action · API key auth

Extract text and structured content from PDFs, images, and Office files using Pulse OCR. Returns clean markdown, page counts, layout bounding boxes, chunks, and extracted figures.

Put Pulse to work View Pulse integration docs

Overview

The ModuleX Pulse integration lets a ModuleX agent operate Pulse on your behalf — working across parsers — directly from a plain-English request, using your organization's own Pulse credentials. No pre-built workflow is required: the agent picks the right Pulse action for the task.

Pulse is an ai & machine learning platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Pulse action — or, when you want a repeatable process, the composer assembles a Pulse workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Pulse in plain English

Type what you want. A ModuleX agent picks the right Pulse action — or chains several — and runs it. No workflow to build.

Parse a document (PDF, image, or Office file) from a public URL using Pulse OCR and return clean markdown, page count, layout bounding boxes, optional HTML, chunks, and figures
resolves toparser

Use cases

What you can automate with Pulse

Parse a document (PDF, image, or Office file) from a public URL using Pulse OCR and return clean markdown, page count, layout bounding boxes, optional HTML, chunks, and figuresparser

At a glance

Pulse integration at a glance

VendorPulse

CategoryAI & Machine Learning

Actions available1

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

The 1 Pulse action

Parsers1

parser

Parse a document (PDF, image, or Office file) from a public URL using Pulse OCR and return clean markdown, page count, layout bounding boxes, optional HTML, chunks, and figures.

See full parameters and response schemas in the Pulse integration docs

Two ways

Two ways to use Pulse in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Pulse action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Pulse into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Pulse

API keyPulse uses API-key authentication. You provide your own Pulse secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Pulse without re-authenticating.

Step-by-step setup in the Pulse docs

Pairs well with Pulse

Agents often chain Pulse with these — connect them once and the agent can use all of them in a single task.

Browser Use25 actions

FAQ

Pulse + ModuleX FAQ

A ModuleX agent can run any of Pulse's 1 action — across parsers — from a plain-English request, using your organization's own Pulse credentials.

No. The agent selects the right Pulse action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Pulse API key, stored encrypted and scoped to your organization.

1, spanning parsers.

Pulse runs on your own credentials, so any Pulse usage is billed by Pulse directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Pulse to work in ModuleX.

Connect Pulse once with your own credentials and let your agent run its 1 action on demand.

Put Pulse to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →