FAQ

Can Pulsegrid work with our existing systems?

Yes. Pulsegrid connects through APIs, webhooks, databases, and guarded file exchanges, with explicit fallbacks for systems that need a slower path.
Where does human approval fit?

Any step can pause for an accountable owner, carry the evidence they need, enforce a service level, and record the resulting decision.
How are failed runs handled?

Exceptions are visible at run level. Teams can inspect context, route ownership, retry deliberately, and avoid duplicating completed actions.
Can we start with one workflow?

That is the preferred path. Start with a painful, measurable workflow; prove reliability and ownership; then expand from evidence.

How is access controlled?

Connections use scoped credentials and role-based access. Sensitive values stay masked from operators who do not need them.
What can operators see in production?

Operators can see status, inputs, decisions, timing, retries, and the exact step that needs attention without exposing secrets.
How do changes reach production?

Drafts are tested against representative paths, reviewed, versioned, and published with a clear record of who changed what.
Does Pulsegrid replace our systems of record?

No. It coordinates work between the systems that already own customer, financial, support, and operational records.