Skip to main content
Most teams have information they need to collect, process, and act on. But building a tool that takes someone’s input, does something useful with it, and hands back a result has always required engineering time. With VectorShift Forms, you can do all of that yourself without writing a single line of code. You connect a form to any workflow you have built, and VectorShift handles the rest. The person filling out your form sees a clean, professional interface. Behind the scenes, your workflow runs. It can call an AI model, save data to a table, ping an external API, send a notification, store a record, or any combination of these. The result comes straight back to the user.
If you are new to VectorShift and have not built a workflow yet, start with the Getting Started guide first. This chapter assumes you have at least one workflow ready to connect.

​
What is a form?

A form in VectorShift is a user-facing interface that sits on top of your workflow. It collects inputs from whoever is filling it out, passes them through your workflow, and displays the output back to them, all in one place. Once your form is live, you have several ways to get it in front of the right people:
  • Direct link — share a URL anyone can open in their browser
  • Embed — drop it into any webpage using an iframe
  • Internal marketplace — publish it so teammates inside your organization can discover and use it
  • Portal — deploy it directly to end users who access it through a portal assigned to them
  • Chrome Extension — make it available inside the VectorShift browser extension
  • API — trigger it programmatically from your own application

​
When to use a form vs a chatbot

Both forms and chatbots let people interact with your workflows, but they work differently. A form is the right choice when you want someone to fill in specific fields and get a result back in one go. Think of a loan application screener, a financial report summarizer, or a client onboarding form. The user provides structured information, your workflow processes it, and they get an answer. A chatbot works better when the interaction needs to go back and forth. If someone needs to ask follow-up questions, refine their request, or have a conversation to reach the right answer, a chatbot fits that better. If you are not sure which one to use, a good rule of thumb is: if you can write down every piece of information you need upfront, use a form.

​
What you will find in this chapter

  • Building your first form — how to create a workflow, attach a form interface, and get your form live
  • Personalizing your form — how to customize the layout, styling, and editing experience
  • Sharing your form — how to share the link, embed it on your site, and deploy through other channels
  • Tracking performance — how to read your analytics and understand how your form is being used
  • Reviewing submissions — how to view and manage what people have submitted