Athena 101 · Lesson 14 · Work with websites
Transcript
Transcript
Some sites your team relies on have no API. Athena can still work in them, signed in as you. Here’s what you’ll learn.Save a site’s login once, and Athena can use that site as a signed-in person would. Here, it’s Northwind’s carrier rate portal. Create a browse profile, and give it a clear name. Then sign in once, in the browser below. Click Done, then Save. The profile keeps the login, so nobody pastes a password into a prompt. Make one profile per site and account. Jordan also saves the team’s CRM login for later.When a site asks for a code, you stay in charge. Athena doesn’t guess. You step in. Start a browse session from the profile, and keep Persist changes on. When the site asks for a code, hover the browser and choose Takeover. Enter the code yourself, then release control. The action log records both. With Persist on, the refreshed login is kept for next time. Stop, start again, and check you’re still signed in.Your AOP can use that same login, and only that one. Open its prompt, and hover Web Browser. Choose Select profiles, and pick the carrier portal. Only pick what this job needs. The Salesforce login has no business here. The choice is saved with the AOP. A profile that hasn’t been saved yet can’t be picked. When it runs, check that it opens the profile you expect, signed in.Now the rates land in your sheet, each with its source. Run it once by hand. Open the browser card, and check it used the carrier portal login. Athena reads the rate notices and adds the new ones to the sheet. Each row keeps a link to the notice it came from. Open one and compare it with the page. When the source is a website, that link is how anyone checks a number later, including you, next quarter.No browse profiles in your workspace? The Chrome extension does the same reading in your own tab, signed in as you. It shows its plan as it works, and while Athena acts, you can stop it.Quick check. Mid-session, the portal asks for a code. What do you do? Take over, enter it, then release control.Here’s how a procurement team uses this. They check a supplier portal that has no API. One person saved the login as a browse profile. An AOP adds new price notices to a sheet each week, with a link to each one, so reviewers check the source, not a copy.Now try it, with one of your own browse profiles. When it works, the browser card says using profile, and every new row has a source link.
Before you start
Upload these files from the Northwind starter kit: Lesson 14/Carrier rates.xlsx and Lesson 14/Carrier portal rate notices.html. Follow Workspace setup.txt to prepare the rate-check procedure. Ask your admin for practice-site access and saved browser sign-ins. If saved sign-ins are unavailable, use Athena in your own signed-in browser tab. If the practice site is unavailable, read the supplied notices and update the sheet; login and takeover steps are watch-only.Steps
1
Save the login
Create a Browse Profile and sign in to the practice site. Click Done, then Save Profile, keeping a separate profile for each site and account.
2
Take over when needed
Start a session with Persist changes to this profile on. Use Takeover to enter a requested code, release control, then restart the session to check the login was kept.
3
Choose the right login
In the procedure’s browser settings, choose Select profile(s) and pick only the login this work needs. Save the choice before running.
4
Read and check the updates
Run once by hand and confirm the browser used the expected login. Check the new sheet rows and open a source link to compare it with the website.
5
Use your own tab
If profiles are unavailable, use the Chrome extension in your signed-in tab. Read its plan as it works and click Stop Athena when needed.
Try it
Using my [site] browse profile, open [page] and add each new [item] to @[sheet] with a link to where you found it.Look for using profile: on the browser card and a source link on every new row.