Skip to content
← GoFormz Feedback Portal

Workflow, Integrations & Automations

Workflow, Integrations & Automations Forum! Vote for and comment on existing ideas or enter your own idea below. When entering a new idea please include a brief description and why it is important to you.

For more information on statuses and our review process, check out our user guide.



Workflow, Integrations & Automations

Categories

(thinking…)

How can we improve GoFormz integrations, workflows, and data automation?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

4 results found

  1. Workflow Trigger based on a Form Field

    Ability to trigger a workflow based on a specific form field response.

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Under Consideration  ·  1 comment  ·  Workflow Editor  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Get notified when a Workflow triggered email is bounced or suppressed

    Notification that when an email bounces as part of a workflow. Currently it say that the workflow is complete and doesn't reference the knowledge that it has bounced.

    9 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Under Consideration  ·  0 comments  ·  Integrations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Remove workflow syntax prompts where non-applicable

    In some cases, the workflow builder suggests syntax prompts that are non-applicable to the section in question. For example, with a Get Images Step the image field name should be copy/pasted exactly as is (ex:"Image", not listed in the variable syntax (ex: "#{trigger.Image}"). Similarly, when referencing a SQL Table in the SQL Upsert Row step, you just need to copy/paste the name of the table in SQL. The workflow shouldn't prompt you to enter GoFormz outputs in the variable syntax.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Under Consideration  ·  0 comments  ·  Workflow Editor  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Ability to rerun a workflow from a specific step

    The Idea: Please add the ability to rerun a workflow job from a specific step. For example, if a workflow has 5 steps and fails on step 3, I want to be able to choose where the workflow reruns from. I could have it rerun from step 3, so that steps 1 and 2 are not rerun, or I could rerun it from step 2 so that all steps but step 1 would rerun.

    The Reason:
    We regularly deal with failed workflow steps, the most common of which is Procore File Upload failing and SQL Upserts failing. This is sometimes…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Under Consideration  ·  0 comments  ·  Workflow Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?