Glow for WordPress

For each website: the monthly custom-development allowance, how many minutes have been logged against it this calendar month, and how much is left. Answers "who is over their hours". Work logged as free of charge is counted separately and does not consume the allowance. Use time_summary instead for logged time over an arbitrary period.

time_allowance

A link that takes the agency into a website's WordPress admin, signed in, via Glow. The link goes to Glow, not to WordPress: the sign-in is created when the person clicks it, so nothing reusable is shared here. Give this to the person to click; it will not work for anyone else.

site_login_link

Plugin, theme and core updates outstanding across the fleet, one client, or one website, ordered by the most outstanding first. These are the counts Glow last recorded from each site, not a live check. A site that is not connected still reports the counts from when Glow last reached it: those are historical, not outstanding work, which is why fleet_overview excludes them from its totals.

pending_updates

PageSpeed scores and load times recorded for sites in this agency, desktop and mobile. These are Core Web Vitals measurements, not an SEO audit: Glow does not compute an SEO score and none should be inferred from these numbers.

performance

Report configuration across the fleet, one client, or one website: whether a report is set up at all, how often it runs, when it next runs, who receives it, and which sections are included. Use this to find sites with no report configured, or to answer what is due.

report_schedule

Reports already generated for one website: the period covered, when it was generated, its size, whether it was emailed successfully, and a temporary download link. Delivery status distinguishes sent, partially sent, failed and never sent, which nothing else in Glow surfaces. Returns report metadata and links, not the report contents.

list_reports

Certificate expiry dates for monitored websites, soonest first. Use expiring_within_days to find certificates that need renewing. Only sites with uptime monitoring enabled have certificate data.

ssl_status

Progress of safe updates on one website: which plugins are being updated, what stage each has reached, and when it was last touched. Use after run_safe_update, and give it a moment: a backup and screenshots happen before anything is installed.

safe_update_status

Set how many hours of custom development time are allowed for ONE website each month. This is the figure client reports measure usage against, so lowering it can put a site over its allowance retroactively. Requires the website uuid. Use time_allowance to see the current value and how much has been used first.

set_time_allowance

Hours logged against websites over a period, per site, from the work recorded in Glow. Use for invoicing and for seeing where effort went. This is the COST side only: Glow bills the agency, not the agency's clients, so what a client pays is not in Glow and profitability cannot be calculated from these numbers. Time logged as pro bono is reported separately in pro_bono_minutes and is NOT part of the billable totals, matching how the Glow dashboard counts it.

time_summary

Enable or disable uptime monitoring for ONE website. Disabling stops all checks and all down alerts for that site: nothing will tell you it went offline. Requires the website uuid, which list_websites or find_sites will give you. Use uptime_history to see the current state before changing it.

set_uptime_monitoring

Update named plugins on ONE website using Safe Updates, which takes a backup and screenshots first, verifies the site afterwards, and can be rolled back. Requires the website uuid, which you must get from a read tool first: this tool does not accept domains. List the plugins explicitly by name; there is no "update everything" option. Updates are dispatched in the background, so use safe_update_status to see how they went.

run_safe_update

Update named themes, or WordPress core, on ONE website. These updates CANNOT be rolled back: unlike plugin updates there is no backup, no before-and-after check and no undo, which matches how Glow itself performs them. For plugins use run_safe_update instead, which is reversible. Requires the website uuid from site_updates. Name themes explicitly; there is no "update everything" option.

run_update

Downtime incidents for one website, newest first, with the reason and HTTP status where known, plus the uptime percentage over a recent window. An incident with no end time is still ongoing.

uptime_history

Known vulnerabilities affecting sites in this agency, from the vulnerability feed matched against each site's recorded plugin and theme versions. Excludes ones already marked fixed or ignored.

vulnerabilities

Everything that happened across the estate since a date: work carried out, updates applied, and sites that went down or recovered. Use this for a weekly or morning catch-up rather than asking several tools and stitching the answer together.

whats_changed

One work queue across the whole estate: reports due to send, sites needing attention, sites with the most outstanding updates, backups that failed, and sites that are down. Use this to answer "what needs doing today" rather than calling several tools and combining them.

pending_today

The plugins and themes with an update outstanding on ONE website, named individually with their current and available versions. Use this before run_safe_update: it returns the exact names that tool requires, and the website uuid it needs. pending_updates gives counts across sites; this gives the names for one. Versions are what the site last reported to Glow, not a live check.

site_updates