“Yes. ProcessMaker has a genuinely usable API for integrating external applications, including starting workflows programmatically.”
“ProcessMaker has a genuinely usable API for integrating external applications, including starting workflows programmatically.”
“It is more than just a collection of read-only endpoints.”
“API-driven process initiation: Your application calls ProcessMaker when something happens and starts a workflow, passing the necessary data.”
“Event-driven integration: ProcessMaker interacts with external systems through integrations, connectors, and webhook-style mechanisms.”
“This is explicitly supported in ProcessMaker 4.”
“ProcessMaker provides working examples in Python, Node.js, Postman and cURL.”
“ProcessMaker also documents a dedicated Starting a Request via Web Hook integration.”
“REST API documented using OpenAPI.”
“Swagger UI for exploring and testing endpoints.”
“OAuth 2.0 authentication.”
“Authenticated client applications.”
“Personal access tokens.”
“ProcessMaker calls external APIs during a workflow | Yes, through integrations/data connectors”
“Bottom line: Yes, ProcessMaker can be driven externally through both REST API calls and incoming webhooks.”
“ProcessMaker sends outbound webhooks on arbitrary workflow events | Needs verification for the specific event and implementation”
“My main due-diligence question would be whether its outbound event notification capabilities are sufficiently flexible to avoid building a separate integration/messaging layer.”
