Conditional Form Logic

Formstack forms branch based on how someone answers earlier questions, sending different applicants down different paths. A Beam agent watches for completed submissions, reads which branch the form logic produced, and applies the customer's approved rule, for example moving a vendor application to onboarding or a support form to billing. It can update a linked field or status in Formstack and notify the owning team so nothing sits unseen. Submissions where the branch outcome is unclear, contradictory answers, or missing required fields get set aside for a person to resolve before anything moves forward.

Approval Workflow Steps

Formstack workflows move a submission through a sequence of approval steps, each assigned to a specific reviewer. A Beam agent checks a workflow's current step, reads the submission and any prior comments, and applies the approved rule for that stage, such as auto-approving requests under an agreed threshold or reminding the assigned reviewer when a step has sat idle. It updates the step status in Formstack once action is taken. Requests above the threshold, missing documentation, or flagged by an earlier reviewer are left in place for a person to decide, with the reason noted for context.

Submission Notifications

Formstack can alert a team when a form is submitted, but deciding who needs to see it and what happens next is still manual. A Beam agent reads the submission's field values, applies the customer's approved rule to work out the right recipient or downstream system, such as forwarding a vendor form to procurement, and updates the submission's owner field in Formstack. It records the action taken so the team has a reference. Submissions with unusual field combinations, missing required answers, or no matching rule are routed to a person to assign manually, with the details attached for context.