Option generator workflows

Were you a Rewst Classic user? The new way to set up and use option generator workflows in the platform is to ask the Rewst Agent to do the work for you. The below information and steps will help you understand what they are and why to use them, essential knowledge for talking to the Rewst Agent.

An option generator workflow is a workflow whose only job is to produce the list of choices that appear in a form field's drop-down instead of you hard-coding a static list. Think of a form field like "Which company?" You could type all your companies in by hand, but then you have to edit the form every time a company is added or renamed. Instead, you point that drop-down at a workflow. When someone opens the form, Rewst quietly runs that workflow, it goes and asks your PSA "give me the list of companies," and the answer becomes the drop-down list. Always current, no manual upkeep needed.

An options workflow must use the Request Options trigger. If you build it with a form or manual trigger, the drop-down won't be able to use it.

Create an option generator workflow

Part 1: Build the workflow

1. Navigate to to Automations > Workflows in the left side menu of your Rewst platform and create a new workflow. Name it something obvious like Options - Companies .

2. Drag and add the Request Options trigger to the Workflow Builder Canvas as the starting node.

3. Connect one action node that fetches the list you want — for example, a list companies action from your PSA integration, or list users from Microsoft.

4. Publish the workflow. Note that a workflow that has never been published falls back to its latest draft. Once a version is published, later unpublished edits are ignored.

Part 2: Point your form field at the workflow

1. Open your form and click the drop-down field you want to populate.

2. In the field's settings, find the Options area and switch the source from a manual/static list to Workflow.

3. Pick the workflow you just published.

4. Now, tell Rewst which piece of each record to use.

   • Value: the hidden bit the automation actually uses. This is usually id.

   • Label: the friendly bit the human sees. This is usually name or displayName.

   When a company record comes back as id: 19297, name: "Pedro Aviary" , the user sees Pedro Aviary, and your workflow receives 19297.

5. Use the field's preview to confirm that real names appear, then publish the form.

Helpful hints

• Empty doesn't always mean something is broken. If the workflow runs fine but the list is empty, it usually means there genuinely aren't matching records, not that you wired it wrong.

• Long lists are paged. Rewst won't dump 5,000 records at once. Instead, it loads more as the user searches or scrolls.

What is a dependent drop-down?

The most common follow-up to a simple option generator workflow is to ask the Agent to "Pick a company, then only show contacts at that company." Setting this up is the same idea as a basic option generator workflow, with one addition. The second workflow accepts an input, like companyId, and on the form you bind the first drop-down's answer into that input. When someone changes the company, the contacts list re-runs and refreshes itself.