Skip to main content

FAQ: How do I use Workflow Forms for sharing?

If you're seeking to incorporate artificial intelligence (AI) into workflows more effectively, consider "Magic Forms." These are tools designed to allow the easier structuring of AI-driven workflows, both within your enterprise and externally.

Understanding Workflow Forms

Magic Forms serve to simplify the task of constructing custom forms that link to specific workflows. This in turn allows various users - colleagues, clients, or customers - to employ powerful workflow tools such as transcript summarizers or lead enrichment capabilities.

Workflow

Forms for Internal Use

Embedding Magic Forms into your business's internal systems offers your team a range of AI-based tools. Here are examples:

  1. Transcript Summarizer: This tool allows users to run recorded conversations through a dedicated workflow. The result is a compressed summary of the conversation.

  2. Content Idea Generator: Those in content marketing can use this form-equipped workflow to develop creative content ideas based on key inputted words or themes.

Using Magic Forms Externally

Creating externally-facing Magic Forms can provide your existing or potential customers with valuable services. Here are a couple of common applications:

  1. Sales Intake Form: You embed this Magic Form on your site, letting incoming customers input their details. The connected workflow processes the lead, adds it to the CRM, assigns a category, and sends a response.

  2. Customer Support Query Form: By placing this Magic Form on a site, you can accept customer queries, process them, and direct the queries to the relevant departments for swift resolution.

Benefits of Magic Forms

Using Magic Forms for your workflows has several key advantages:

  1. Process Streamlining: Magic Forms drive efficiency by speeding up both internal and external workflows.

  2. Improved Data Management: Thanks to embedded AI functions, Magic Forms enhance the accuracy of data entry and reduce the chance of human errors.

  3. Ease of Use: Magic Forms are designed to be used without technical expertise, making it easier for all stakeholders to utilize these tools.

  4. Customizability: You can modify these forms to suit your business's needs, ensuring compatibility with your infrastructure.

  5. Greater Accessibility: Magic Forms afford a wider range of users access to advanced data processing workflows.

The use of Magic Forms within your AI workflows can deliver greater efficiency, improved accuracy, and a superior user experience. They provide a convenient and effective way to make AI systems more accessible and efficient within your organization.

Is it possible to have workflow that asks for input from the user not just at the start of the flow with a form, but throughout the flow after each process steps, so it can pose questions relevant to the last input provided?


Hi teemac,

That’s an interesting question.  What you’re describing is ultimately a co-pilot experience which would essentially be our Chat which is intended for a 1:1 human exchange with an LLM.  Conversely, our Workflows are an auto-pilot experience, a 1:many human to LLM exchange, primed for automation.  This solves fundamentally different use cases and, with a dramatic increase in compute on the LLM side, delivers compounding value.  That said, we do have a roadmap item logged where Workflows can be triggered by Chat, so I think what you’re after will in fact be possible in the future. I hope that helps!

Chris


What would be useful is a multi-step form so it does not feel like a lot of input is collected in one huge list. I’m wondering whether this can be achieved with a form triggering a workflow that presents another form, and so on? the final workflow would then process all the information from all the workflow forms. Is this possible? I don’t necessarily need it to process the information from the previous forms, until the very end workflow.


Right now, there are only two ways to accomplish this:  First, you could interface with the workflows completely via API and build a UI that outputs multiple forms in order to coordinates the workflow processing in an OEM fashion.  Alternatively, you could use the embed code to insert multiple forms in a single page (webpage, intranet, blog post, etc), run each, and then copy and paste the results into the final workflow.  While we have UI interaction improvements planned, those are the two solutions at this time.  However, I will pass your suggestion along to the Product team.  Thanks for reaching out!


Reply