Skip to Content
Settings and billing

Add a module

A module finds bids or companies for your workspace. Add it in Settings, Scouts, try it in Trial, then move it to Live.

A module is a small package that finds records of one kind at a source: the open tenders of a public register, or the companies in a feed of news. A developer writes it. Tommos runs it on the schedule you set, checks every record it gives, and keeps a log of each run.

KindWhat a record isWhere it goes when the scout is Live
BidsAn open tender, for Tommo BidsThe triage of Tommo Bids, then a deal on the board of the page Bids
ProspectsA company, for Tommo SDRA company in Found on the board Prospecting

A developer starts from the reference module. Modules is their guide.

The list of scouts

Open Settings, Scouts. Each scout shows its name, its kind and the tommo it works for, what its last run did, and its state: Trial, Live or Stopped. Press a scout to open its page.

When HigherGov is connected, it stands first in the list. It opens its own settings in Settings, Bids. See Connect HigherGov.

Add a module

Only an owner or an admin of the workspace adds a module. Other people see who can.

  1. The developer gives you the link to the module's public repository on GitHub and a tag, such as v0.1.0. A zip of the module works too.
  2. Under Add a module, choose A repository and its tag or A zip file.
  3. Enter the Repository and the Tag, or pick the Zip file.
  4. Press Check and add.

Tommos runs the module on the examples it carries, in about a minute. It adds the module only when every check passes. When a check fails, the screen says Refused, names each failed check in words, and adds nothing. Give those words to the developer. A private repository cannot be read yet: ask for a public one, or a zip.

When the module is added, it is a scout in Trial. The screen links you to its page to fill its secrets and set its schedule.

Secrets and the schedule

On the scout's page:

  • Secrets lists each secret the module needs, such as the API key of the source. Fill each one and press Save. Tommos keeps it encrypted, and the screen shows only its last four characters. The module sees this value and nothing else of the workspace.
  • Schedule says when the scout runs. Pick Every hour, 6 hours, 12 hours, day or week, and a time From, in London time. Tommos runs the module only when its time comes.
  • Spend on the model, a day shows for a module that asks a model. It sets the most the scout spends in one day. A call past it is refused, and the run goes on without it.

Trial

A new scout starts in Trial. It runs on its schedule, and its records go to the trial lane only: a bid makes no deal, and a company makes no card on the board. The page says when the first trial runs. Run the trial now runs it at once, and after the trial ran, Run again now runs it again. See Run a scout now.

The trial lane stands beside its board: Trial lane with its count on the page Bids, or on the board Prospecting in Companies. The report links to it under Where the records are.

After its first runs, the Trial report shows:

  • the runs, and how many failed;
  • the records found: taken into the trial lane, the same again, and refused;
  • each reason a record was refused, with its count;
  • the links that do not open;
  • how fresh the records are: the newest and the oldest;
  • for bids, how many of them the triage of Tommo Bids sorts Ours;
  • for a module that asks a model, the cost of one run and of a month at this schedule.

Move to Live

When the report looks right, press Move to Live. Only a person moves a scout to Live, and only after the trial ran; until then the page says why the button waits. Its first run in Live comes at once and takes the trial lane's good records too. A scout in Live sends its bids to the triage of Tommo Bids, and its companies to the board Prospecting.

Stop this scout, last on the page, stops it: nothing is read until a person starts it again with Start in Trial.

Run a scout now

An owner or an admin can run a scout outside its schedule. In Trial the button is Run the trial now, and after the trial ran, Run again now. In Live the button is Run now. A member sees no button.

A run now goes as a run of the schedule goes. In Trial, its records go to the trial lane. In Live, its bids go to the triage of Tommo Bids, and its companies to the board Prospecting. The next run of the schedule does not move.

After you press it, the run comes within five minutes. Until then every run button is locked, and the page says when you asked. Each run now is a line of the scout's log, and the line names the person who asked.

Tommos refuses a run now in words:

  • a stopped scout: «Name is stopped. Start it in Trial first.»
  • a run under way: «Name is running now. Its run is in its log when it ends.»
  • a secret not filled: «Fill its secrets first: the secrets.»

A new version

The developer pushes a new tag. Press Update module beside the version on the scout's page, give the Repository and the Tag, or press Give a zip instead, then press Check and update. Tommos runs the same check first, and the running version stays until the new one passes. Adding the module again with the new tag under Add a scout works too. A new version of a Live scout that passes the check stays in Live, with its schedule and its secrets. When a module uses an old version of the tools, its page says so.

When a scout goes wrong

  • A Live scout that fails, or finds nothing, on several runs in a row is told to the owners the same day.
  • A Live scout whose run refuses more than half of its records, of 10 records or more, goes back to Trial by itself, and the owners are told.

The log

The scout's page shows its last run. Every run and every record opens The log: a table of the scout's lines, the newest run first.

  • A line of each run: how it ended (Done, Failed or Out of time), how long it took, and how many records it found, took, saw again and refused. Only a run that failed or ran out of time is red. A run that ended with a warning is done, and it is not red.
  • Each warning of the module is its own line under its run, once. A warning that repeats says how many times, such as Warning ×2. The line shows the first part of the warning; its whole words stand behind Technical details.
  • A line of each record, under its run: Taken, with the link to its deal or company; Same again; Refused, with the reason; or Trial lane. Matched says the rule of the module that took it.
  • For a bid, the line of the triage, under its record: Ours or Not ours, and why. A triage older than its run says its day in its words, such as «Sorted on 12 Nov 2026, 18:00.», and its When stays empty.
  • A record or a triage does not say again the time or the name of the line above it. When a filter shows it without that line, it says its own.
  • Technical details on a run's line: the module version, the tools version, the warnings whole, what the module read, what it dropped and why, and the model calls.

The count of lines, Columns and Download CSV stand together on the line of the span of days, at its right; the search and the filters have the line below. On a phone they stand on their own line under the filters.

Narrow the log by Run to read one run whole. Older runs opens the runs before. Download CSV takes the lines into a file; see Download a log. No secret stands in the log.

On this page