Greatwait home pagelight logo
  1. Quickstarts
  2. Website quickstart

This walkthrough gets you to first value with no code: you create a one-shot schedule in the dashboard at https://app.greatwait.dev, then read the delivery attempt Greatwait made to your receiver.

​
What you need

  • A Greatwait invitation. See The invited alpha.
  • An HTTPS receiver of your own. It must be reachable from the public internet on port 443 and answer a POST with a 2xx status. Greatwait does not provide one.

​
1. Accept your invitation and sign in

Open the link in your invitation. You may be asked to confirm you are human first.

  1. The first screen asks you to set a password. Enter one and choose Continue.
  2. The next screen asks you to set up your organization. Enter its name and choose Continue. A logo is optional.

You are then signed in to the dashboard.

If you were already signed in with a different account, the dashboard says the invitation is not for that account and offers to sign you out. Sign out, then open the invitation link again.

​
2. Create a project

A new organization has no projects, so the dashboard opens on Make your first project. Enter a name under What do you want to name your project? and choose Create project.

The project opens on its Overview, with a panel called Get to your first callback. It lists three steps: Add an endpoint, Schedule a one-shot, and See a callback arrive. The step you are on is marked next and shows its action button, and finished steps are marked done.

​
3. Create a destination

In the dashboard a destination is called an endpoint.

  1. In the checklist, choose Add an endpoint.
  2. Under Address, enter your receiver’s HTTPS URL. Name is optional: left empty, the endpoint is named after its address.
  3. Choose Create endpoint, once. An endpoint without a name takes its address as its name, and names are unique, so a second press is refused even though the first endpoint was created.

The Endpoint created screen shows the endpoint’s Key id and its signing Secret. Choose Copy and store the secret where your receiver can read it, for example as an environment variable. Your receiver uses it to check that callbacks came from Greatwait; see Verifying callbacks. If you lose it, you can reveal or copy it again from the endpoint’s page.

Choose Done. This opens the endpoint’s page under Settings. Choose Overview in the sidebar to return to the checklist.

If the address is refused, nothing is created and what you typed stays in the form. An address that does not start with https:// is refused before anything is sent; other refusals say Nothing was created. Check that the URL uses HTTPS on the default port, has no username, password, or fragment, and resolves to a public address.

​
4. Schedule a one-shot

  1. In the checklist, choose Schedule one.
  2. Under When it fires, keep After a delay, once. Under Delay, enter a short delay such as 30s. A plain number means seconds.
  3. Under Endpoint, choose the endpoint you just created. If you leave it empty, the schedule is a timer that delivers nowhere, and no callback is made.
  4. Optionally, add a JSON Payload to send with the callback.
  5. Choose Create schedule.

Before you save, When this will run beside the form shows when it will fire. After you save, the dashboard opens the new schedule’s page.

​
5. Watch the callback and read the attempt

Choose Overview in the sidebar. The checklist’s last step, See a callback arrive, is now next, and a Watching for your callback panel says the dashboard is checking every few seconds for about three minutes. You can leave the page: the occurrence keeps the result either way.

To open the occurrence while the dashboard is watching, choose Watch for it. Once the callback has succeeded, the checklist is complete and no longer appears on the Overview. To find the occurrence after that, choose Schedules in the sidebar, open your schedule, and choose the run listed under Occurrences.

The occurrence page shows:

  • Its status, such as Delivered, with a sentence explaining it.
  • Planned for, Lag, Settled, and Attempts, which counts the attempts made and how many are left.
  • Under Attempts, each delivery attempt: when it started, how long it took, and the status your receiver answered.

An attempt marked Accepted, with your receiver’s 2xx status under answered, is first value: the callback was made, your receiver answered, and the outcome is recorded.

If the delivery did not succeed, the Overview says so and links to the occurrence. The attempt shows what your receiver answered and how the failure was classified. Failures and retries explains what to do next.

If the dashboard stops watching before anything arrives, that does not mean delivery failed. Check again, or open the occurrence later.

​
Next steps