Tines Academy › Lesson
Choose how it all starts
Help Sue in operations collect vendor requests through a form instead of chat, with every submission saved to a request list.
Objective: Choose a suitable trigger for a workflow and describe its expected result in a way you can test.
Where you’re starting
Sue works in operations. Teams send her vendor requests in chat, usually missing half the details she needs. She copies each one into a spreadsheet, checks whether someone already asked for the same vendor, chases managers for approval, and messages everyone to keep them updated.
In this learning path, you’ll build her a tracker that keeps all of that in one place.
Where you’re headed
With a full brief, Tines 3B could build Sue’s whole tracker in one go. We’ll take it one stage at a time, so you can practice describing what you need and checking the result.
As you build, you’ll limit what the tracker can do, check that requests reach the right people, and decide who keeps it current. These habits help people use the tracker without exposing information or doing something they shouldn’t. Each lesson ends with a Build it safely note about a habit you’ve practiced.
First, you’ll build a request page so everyone submits the same details. By the end of the path, you’ll have a tracker that looks something like this.
Key terms
Four ways to start a workflow
Describe the result you want
Sue’s workflow starts when someone submits a request. You’ll build the tracker in the stages shown below, starting with the request page and list. When this first stage works, the requester will see a confirmation, and Sue will see the request in her list.
Be specific about what you want to happen and where you expect to see it. That gives Tines 3B clear instructions and gives you something concrete to check when the build is ready.
Before you start building:
Open your Tines 3B tenant. If you don’t have one yet, sign up for one.
Choose a space where you can build and where your chat connector is available if you plan to use one. Otherwise, your personal space is fine.
Use your own name and made-up vendor details. Use example.com, example.org, or example.net for vendor websites and email addresses.
If you connect a chat tool, use a channel where you can safely send test messages. You can also complete the path with message previews only.
Keep the workflow as a draft while you work through the path. You don’t need to publish it to complete the learning activities.
Build the request page and list
From Home, open the space where you’ll build.
Paste the prompt into the chat box and send it to create a new workflow. If you’d prefer to review a plan first, turn on Plan mode before sending it.
Build a vendor request tracker for our operations team. For now, just a request page and a list of requests.
Ask for the requester’s name and team, the vendor’s name, website, and contact email, what they’re buying, and the estimated annual spend in US dollars. Use the signed-in account to identify who submitted each request.
Save each request in the workflow's storage with an ID and status "New." Show the requester a confirmation with that ID and the details they entered. Show the newest requests first in the list. Add two sample requests with made-up vendors.
Keep the pages private to this space. Don’t contact vendors or visit their websites.
It works when a test request appears in the list as "New" and is still there after a page refresh.
Keep the workflow as a draft. Summarize how requests are saved, what the confirmation shows, who can open the pages, and anything you couldn't verify.
Check the result
Read the build summary in workflow chat. Look for how requests are saved, what the confirmation shows, and who can open the pages. Note anything Tines 3B couldn’t verify.
Submit a request
Open the request page in Browser.
Use your own name and team, with made-up vendor details. Use example.com, example.org, or example.net for the vendor’s website and email address.
Submit the form.
Check the confirmation
The confirmation should show your request ID and the details you entered.
Keep the ID handy so you can find the same request in the list.
Find the saved request
Open the list page in Browser.
Check that your request appears at the top with the status “New.” Its ID and details should match the confirmation.
Refresh the page. The request should still be there.
Find the sample requests
Check that the two made-up sample requests are also in the list.
Keep these and your own test request. You’ll use them to try the review process in the next lesson.
If something doesn’t match
Tell Tines 3B what you entered, what you expected, and what you saw. Ask for a fix, then repeat the affected check.
Ask it to record unfinished checks in Readme.
You’ll keep building Sue’s tracker in the next lesson. Now think about a task you’d like to automate. You’ll answer a few questions about it as you work through the path. At the end, we’ll use your answers to create a brief you can give Tines 3B to start building your own workflow. Leave out passwords, tokens, and personal details.
What to do if something still feels fuzzy
You built Sue’s request page and checked that it saves submissions to her list. Before building, you chose how the workflow would start and described a result you could test. Next, you’ll build a request review step for operations.
Build it safely: You kept the tracker as a draft with access limited to your space, used made-up vendor details, and tested the page after Tines 3B built it.