Only account admins can perform this task.
Some condition, activity, and approval nodes may be restricted to Premium or Pro plans. Your company must have one of these plans to incorporate them in your workflow.
The workflow designer uses nodes to determine the business logic applied in processing expenses in Perk.
When you create a workflow, you use four types of node:
- Status nodes: Indicate the document’s status. In other words, these nodes represent Perk internal statuses (e.g. Draft, In approval, etc.).
- Condition nodes: Represent conditional clauses. They are if-else conditions based on specific logic that is either true or false.
- Activity nodes: Represent actions or tasks behind the scenes in Perk.
- Approval nodes: Complement activity nodes to reproduce the business logic of an approval flow.
Status nodes are common to both invoice and expense workflows. Condition, activity, and approval nodes are specific to each workflow type.
Each status node has a specific combination of nodes that can be placed before and after. The action that can be triggered depends on this combination. The workflow designer allows these combinations for expense workflows:
| Status node |
Incoming node / action |
Outgoing node / action |
|---|---|---|
| Draft |
|
|
| In review |
|
|
| Needs revision |
|
|
| Ready for expense export |
|
|
| Ready for transaction export |
|
|
| Expense exported |
|
|
| Transaction exported |
|
|
| Rejected |
|
|
| Archived |
|
|