SETUP TIME · ~10 MINUTES

Signup to scanning,
in about ten minutes.

Five short steps walk you from creating your account to a running bot. Everything below mirrors the screens you'll actually see — no marketing fluff, no fake screenshots.

Start setup nowAsk a question first
STEP 01~2 MIN

Create your FlexGuru account

Email + password. If your admin has email verification turned on you'll get a 6-digit code by email — otherwise you go straight to the dashboard. No phone number, no card needed yet.

  • Email + password (no SSO yet — coming soon)
  • OTP code emailed if verification is enabled in admin settings
  • Pick the home region you'll drive in
  • Logged straight into the setup wizard on first sign-in
PRO TIPUse the same email Amazon Flex knows you by — easier when you need to ask support to look something up.
STEP 02~3 MIN

Link your Amazon Flex session

This is the step everyone gets stuck on the first time. You'll sign in to Amazon on Amazon's own login page, then copy the URL you land on back into FlexGuru. Amazon never sees FlexGuru in the middle — you authenticate directly with them.

  • Pick your Flex region (AU / US / UK / CA)
  • Click 'Open Amazon Flex Login' — opens a new tab on amazon.com.au (or .com / .co.uk / .ca)
  • Sign in on Amazon's real domain with your driver credentials
  • After sign-in the page may look blank — that's expected
  • Copy the full URL from the address bar (contains '/ap/maplanding')
  • Paste it back into FlexGuru and click 'Connect Account'
PRO TIPIf the landing page looks blank or shows a friendly Amazon message, don't panic — the auth code is in the URL itself. Just copy the address bar.
STEP 03~2 MIN

Set one filter (conservatively)

Don't try to grab everything on day one. Pick ONE station you actually like driving to, set a minimum pay you're genuinely happy with, and leave the more aggressive options off until you have a few days of data.

  • Pick ONE station first (not all of them — narrows the noise)
  • Set 'min pay' conservatively (e.g. A$80 for a ~2-hour block)
  • Leave 'startToday' OFF — let it grab tomorrow's blocks first
  • Pick block lengths you'll actually drive (3.5h / 4h / SDL)
PRO TIPMore filters = more REJECTED rows = looks like the bot isn't doing anything. It is — the rejection log is proof of work.
STEP 04~1 MIN

Schedule a 1–2 hour window

Don't run the bot 24/7 from the start. Pick a window when you'd actually be willing to drive — early morning or evening — and let it scan during that slot only. You can always widen it later.

  • Choose a single 1–2 hour window per day to start
  • Pick hours you'd already be willing to drive
  • Add a second window for weekends if you want
  • Bot only scans during your window — no requests outside it
PRO TIP5–7am and 6–8pm tend to surface higher-pay blocks. Schedule for one of those, not midday.
STEP 05~30 SEC

Press START and watch /blocks

Hit the green Start button on the dashboard. The bot wakes up, picks up your filter + schedule, and starts scanning Amazon for offers. Every offer it sees gets logged on the /blocks page as ACCEPTED, REJECTED, or MISSED — so you can see in real time that it's working.

  • Dashboard bot status flips to green
  • Open /blocks — rows appear as offers are evaluated
  • ACCEPTED = you got it · REJECTED = filter excluded · MISSED = lost the race
  • Pause any time from the dashboard — takes one click
PRO TIPGive it the first 24 hours before you judge it. The bot eases in — it starts cautious and settles into a natural pace as it gets a feel for your account.

Lots of REJECTED rows is the bot working, not a bug.

Drivers expect a wall of ACCEPTED on day 1. Reality: a wall of REJECTED, a handful of MISSED, maybe one or two ACCEPTED. Here's how to read your /blocks page so you don't panic.

REJECTED

Most rows. The bot saw the offer, but your filter excluded it (pay too low, wrong station, wrong block length). This is the filter doing its job. Expect dozens to hundreds per day.

MISSED

Offer matched your filter but another driver — or another bot — grabbed it first. A few of these per day is normal, especially in metro markets. Lots of MISSED means demand is hot in your region.

ACCEPTED

The bot grabbed the block for you. 0–2 on the very first day is realistic — the bot is still warming up and your filter may need a tweak. Look for ACCEPTED rows to climb across days 2–7.

Sanity check after 24 hours. Open /blocks and confirm you have any rows. If the page is empty, the bot isn't scanning — check that you pressed START, that your schedule window covers the current time, and that your Amazon connection still shows green on the dashboard.

The four things people get stuck on (and the fix)

Amazon login page looks blank after I sign in

That's expected. After Amazon authenticates you, it redirects to a 'maplanding' page that often appears empty. The information FlexGuru needs is the URL itself — copy the full address from your browser's bar and paste it back into the Connect screen.

I get 'Connect failed — please try again from the start'

The PKCE verifier in your session expired or didn't match. Go back to the Connect page, click 'Open Amazon Flex Login' fresh, sign in again, and paste the new URL. Don't reuse an old URL from a previous attempt.

After 24 hours my bot has only REJECTED rows, no ACCEPTED

Almost always means your filter is too tight for your region. Try lowering min pay by A$5–10, adding a second station, or relaxing the block-length list. REJECTED isn't a bug — it's the bot saying 'I saw an offer, your rules excluded it.' Loosen the rules until ACCEPTED rows appear.

I need to pause for a few days

Hit STOP on the dashboard. The bot stops polling Amazon immediately, no fees, no scans. Press START again when you want to resume — your filter and schedule are preserved. You can also schedule a window that simply excludes the dates you're away.

Five steps. About ten minutes. Then it's the bot's job.

No card needed for the 3-day trial. Commission only kicks in on blocks the bot actually grabs.

Start your free trialAsk a question first