Get Started with ProcessMaker
Watch our videos to quickly get started with ProcessMaker.
Get started with ProcessMaker by watching our videos how to do technical and advanced functions. Visit this page often to see new videos. Please note that some videos may display proof-of-concepts and/or slightly outdated user interfaces; use these videos for educational purposes only and not for your production development.
Videos are organized into sections based on their content.
This section contains marketing videos for your eye-candy pleasure.
Create a Process
"Expense Report" Request
"Purchase" Request
- Intended audience: General and new users
- Viewing time: 1 minute; no narration
- Tags: create Process; create workflow; Process design; design Process; workflow design; design workflow; video
- Intended audience: General and new users
- Viewing time: 3 minutes to watch the three-part video series; no narration
- Tags: start Request; start Process; workflow; Expense Report Process Request; HR; human resources; financial; approval; rejection; Process approval; PDF Generator connector; video
- Intended audience: General and new users
- Viewing time: 5 minutes to watch the five-part video series; no narration
- Tags: start Request; start Process; start workflow; Purchase Process Request; HR; human resources; financial; approval; rejection; Process approval; video
This section contains videos discussing Process development proof-of-concepts and ideas how to use ProcessMaker.
Analyze Documents using RPAs
Call Third-Party APIs with Data Connectors
See how ProcessMaker integrates with third-party services Amazon Textract and UiPath Robotic Process Automation (RPA) so a loan application workflow scans, analyzes, and intelligently routes a Request and provision a bot accordingly.
- Intended audience: Process designers and business analysts
- Viewing time: 11 minutes; contains narration
- Tags: Process design; design Process; workflow design; design workflow; form; web form; design form; form design; analyze documents; Load Application Process Request; API; application program interface; third-party API call; RPA; robotic process automation; banking; financial; loan application; demo; video
See how ProcessMaker integrates with third-party RPA service Automation Anywhere (AA) so a loan application workflow submits a loan request candidate's name to AA to automatically search the Office of Foreign Assets Control (OFAC) site to determine if that candidate is sanctioned from financial transactions, receives AA's response, and then intelligently routes a Request accordingly.
- Intended audience: Process designers and business analysts
- Viewing time: 16 minutes; contains narration
- Tags: Process design; design Process; workflow design; design workflow; form; web form; design form; form design; analyze documents; Load Application Process Request; API; application program interface; third-party API call; RPA; robotic process automation; banking; financial; loan application; demo; video
See how Data Connectors call third-party Application Program Interfaces (APIs), and then use that data in Processes.
- Intended audience: Process designers, business analysts, software developers, coding engineers
- Viewing time: 9 minutes; contains narration
- Tags: Process design; design Process; workflow design; design workflow; form; web form; design form; form design; Data Connector; API; application program interface; third-party API call; Screen Builder; Select List control; demo; video
This example demonstrates dependent fields: how the options in one Select List control depend on which option is selected from a previous Select List control. This example demonstrates how a Select List control in a Screen can display the names of major universities around the world as its options in a drop-down menu. The options in this Select List control come from a Data Connector that calls a third-party Application Program Interface (API) when the Screen containing the Select List control opens.
- Intended audience: Process designers, business analysts, software developers, coding engineers
- Viewing time: 9 minutes; contains narration
- Tags: Process design; design Process; workflow design; design workflow; form; web form; design form; form design; Data Connector; Screen; Screen Builder; Select List control; dependent controls; dependent fields; API; application program interface; third-party API call; higher education; demo; video
Using Screen Builder
Create a Leave Request Form
Populate a Record List from a Collection
Design Dependent Fields
Using Watchers
- Intended audience: Process designers, Web designers, graphic designers
- Viewing time: 3 minutes; no narration
- Tags: form; web form; design form; form design; Screen; Screen Builder; Leave Request form; Leave of Absence Request form; employee information; video
- Intended audience: Process designers, Web designers, graphic designers
- Viewing time: 3 minutes; no narration
- Tags: form; web form; design form; form design; Screen; Screen Builder; Leave Request form; Leave of Absence Request form; employee information; video
- Intended audience: Process designers, Web designers, graphic designers, software developers, coding engineers
- Viewing time: 10 minutes; contains narration
- Tags: form; web form; design form; form design; Data Connector; Collection; Screen; Screen Builder; Record List control; demo; video
This example demonstrates dependent fields: how the options in one Select List control depend on which option is selected from a previous Select List control. This example demonstrates that after a country is selected from one Select List control, a second Select List control contains as options the states and/or provinces in that selected country.
The Select List control that contains the countries as its options gets those options from a Data Connector that uses an Endpoint to get the list of countries and their corresponding ISO codes from a third-party application program interface (API). A Watcher monitors when a country is selected, and then another Data Connector uses an Endpoint to get the list of states and/or provinces from that selected country based on that country's ISO code. The Watcher stores that list of states/provinces as a Request variable in that Request's data so that the second Select List control may access that list to display as its options. The second Select List control's options depend on the first Select List control's selection.
- Intended audience: Process designers, Web designers, graphic designers, software developers, coding engineers
- Viewing time: 21 minutes; contains narration
- Tags: Data Connector; Screen; Select List control; dependent controls; dependent fields; API; application program interface; third-party API call; demo; video
This example demonstrates dependent fields: how the options in one Select List control depend on which option is selected from a previous Select List control. This example demonstrates how a Select List control in a Screen can display the names of major universities around the world as its options in a drop-down menu. The options in this Select List control come from a Data Connector that calls a third-party Application Program Interface (API) when the Screen containing the Select List control opens.
- Intended audience: Process designers, Web designers, graphic designers, software developers, coding engineers
- Viewing time: 9 minutes; contains narration
- Tags: Data Connector; Screen; Select List control; dependent controls; dependent fields; API; third-party API call; higher education; demo; video
See how to use Watchers in Screen Builder to monitor when a Screen control changes value, then perform an action with a Script or Data Connector.
- Intended audience: Process designers, Web designers, graphic designers, software developers, coding engineers
- Viewing time: 9 minutes to watch two videos; contains narration
- Example 1: 2 minutes
- Example 2: 7 minutes
- Tags: form; web form; design form; form design; Process design; design Process; workflow design; design workflow; Data Connector; Screen; Script; Screen Builder; Select List control; Watcher; application program interface; API; demo; video
This section contains videos discussing Vocabulary design.
Using Vocabularies
See how to design a Vocabulary that uses a JSON schema to validate that Request data complies to specific requirements.
- Intended audience: Process designers, software developers, and coding engineers
- Viewing time: 15 minutes; contains narration
- Tags: data validation; data compliance; form design; Screen; Screen Builder; Process modeling; video
This section contains videos how to use the RESTful Application Program Interface (API) and ProcessMaker's Software Development Kits (SDKs). Every function that you may do in ProcessMaker's elegant and well-designed user interface makes an API call. Since every function is supported in our API, ProcessMaker can be white-labeled to run behind the scenes from other SaaS applications. Learn how you can use our API.
Start a Request Via the API
Use the PHP SDK
Access the Database Via the API
Use the JavaScript SDK
Use Script Executors
- Intended audience: Software developers and coding engineers
- Viewing time: 2 minutes; contains narration
- Tags: start Request; start Process; start Request via API; start Process via API; start workflow; start workflow via API; API; our API; application program interface; process_events; Process ID; ProcessID; curl; JSON; token; bearer token; demo; video
- Intended audience: Software developers and coding engineers
- Viewing time: 2 minutes; contains narration
- Tags: PHP; SDK; software development kit; Script; Script Editor; API; our API; application program interface; getProcessesRequests; token; bearer token; demo; video
- Intended audience: Software developers and coding engineers
- Viewing time: 4 minutes; contains narration
- Tags: JavaScript; JS; Node; SDK; software development kit; Script; Script Editor; API; our API; getProcessesRequest; application program interface; token; bearer token; demo; video
Use a Script Executor to call the Google API that requires a custom Google class called Google Client. See how Script Executors can securely run custom code or packages that a sanctioned third-party Application Program Interface (API) or Software Development Kit (SDK) requires to successful call that resource.
- Intended audience: Administrators, software developers, and coding engineers
- Viewing time: 3 minutes; contains narration
- Tags: JavaScript; JS; Node; R; Python; Lua; PHP; SDK; software development kit; Script Executor; Script; API; Google API; application program interface; demo; video
This section contains videos discussing how to administer ProcessMaker.
Administer Script Executors
Custom Script Executors
Use a Script Executor that includes a Docker RUN command to package the Google Client class provided by Google into that Script Executor, thereby allowing Scripts using that Script Executor to successfully call the Google Application Program Interface (API).
- Intended audience: Administrators, software developers, and coding engineers
- Viewing time: 3 minutes; contains narration
- Tags: JavaScript; JS; Node; R; Python; Lua; PHP; SDK; software development kit; Script Executor; Script; API; Google API; application program interface; demo; video
- Intended audience: Administrators, software developers, and coding engineers
- Viewing time: 5 minutes; contains narration