FlowRunner
PricingContact
Theme
Start Free

Award Force

Forms

Connect AI agents to Award Force, a platform for running awards, grants, scholarships, and competitions. Agents register entrants and entries, create categories and chapters, assign judges, and read the rounds, score sets, and leaderboards judging produces.

44 actions API key available
A schedule fires during an open season on the awards program
Agent runs List Entries filtered on season and status to find newly submitted entries
Agent runs Get Entry to read the field values and attachments on each one
Agent tests the entry's category and chapter against the eligibility rules for that season
Agent runs Tag Entry to mark the eligibility outcome and Update Entry to record moderation status
Agent posts the ineligible and borderline entries to the awards manager with the reason
The awards manager approves before any judging assignment is created or removed

What This Integration Enables

Award Force runs awards, grants, scholarships and competitions, and the thing an awards program actually sells is the credibility of its result. That shapes what belongs in a flow and what does not. Agents work the intake and administration side freely: entries are listed with filtering by title, category, chapter, season, entrant, status and payment or review state, read in full with their translated field values and attachments, created on behalf of an entrant, updated across category, chapter, title, status and moderation status, tagged, untagged and deleted. Users covering entrants, judges, managers and administrators are listed, read by slug or email, created, updated, deleted and restored. Categories, chapters and seasons give the program its structure, and categories and chapters are created and updated from a flow. Orders carry the payment side with billing details, discounts and line items, and Update Order writes back to them. Attachments resolve to file tokens, and review tasks expose the moderation workflow items with their reviewer, decision and stage.

Two boundaries matter, and both are load-bearing. First, judging is readable but not writable. List Score Sets, Get Score Set and Get Leaderboard return the judging configuration and the ranked results with per criterion aggregation, and List Rounds and Get Round return the rounds with their chapters and dates, but no action in this connector writes a score, revokes a score, or moves an entry into a round. Judges score in Award Force. What a flow does is assign the work with Create Assignment, remove it with Delete Assignment, and read the outcome. Second, this connector has no triggers. The webhook actions here manage Award Force's own outgoing subscriptions across 27 documented event types, pointing at a target URL and HTTP method you choose, with an optional signing key. They are useful for administering those subscriptions from a flow, and they do not create a FlowRunner trigger and do not make FlowRunner the recipient. Flows against Award Force run on a schedule, using List Entries and List Review Tasks with their filters to find what changed.

Without FlowRunner

Submissions checked one by one Someone opens each entry to confirm the category, the chapter and the required attachments
Eligibility decisions held informally Whether an entry qualifies is agreed in email and never lands on the entry itself
Judge conflicts spotted late A judge assigned to an entry from their own organisation is noticed partway through a round

With FlowRunner

Submissions swept on a schedule List Entries and Get Entry walk the season and read every submission's fields and attachments
Eligibility decisions recorded on the entry Tag Entry and Update Entry write the outcome and the moderation status where judges can see it
Judge conflicts surfaced before assignment List Assignments and List Users are cross checked and the conflict reaches a person first

Use Case Scenarios

Eligibility Sweep on an Open Season

Through an open season, the agent runs List Entries filtered to submitted status and reads each one with Get Entry to pull the field values and the attachment list. It checks the declared category against the entry's own answers, confirms the required supporting files are present, and confirms the entrant holds a matching user record with Get User. Clean entries are tagged and their moderation status recorded with Update Entry. Anything that fails a check reaches the awards manager with the specific rule it failed, rather than being found by a judge halfway through a round.

Judge Panel Preparation

Before a round opens, the agent reads List Score Sets and List Rounds to establish which score set covers which entries, then lists the judges with List Users and the existing pairings with List Assignments. It cross references each proposed judge against the entrants and organisations on the entries in scope and assembles a conflict report. Where the panel is clean, Create Assignment pairs entries to judges across the rounds. Where it is not, the pairing waits. Panel setup that used to be a spreadsheet reconciliation becomes a reviewed list.

Season Reporting and Order Reconciliation

After judging closes, the agent reads Get Leaderboard for each score set with its per criterion breakdown, joins the ranked results against List Entries for category and chapter context, and pulls List Orders to reconcile entry fees against submissions. The result lands in a reporting view built with Google Sheets or Airtable, and the shortlist goes to the committee channel in Slack. The committee sees ranks, criteria and payment state in one place instead of three exports.

Human-in-Loop Highlight

Award Force is the rare system where the record of a decision is more valuable than the decision itself, and Delete Assignment is where that becomes concrete. An assignment links judges to entries within a score set for one or more rounds, and the assignment record carries the judging comments made under it. Deleting the assignment removes the pairing and the work attached to it, and this connector cannot put it back: there is no action here that writes a score, restores a comment, or recreates a completed judging pass. The asymmetry is visible in the action list itself. Delete User has a matching Restore User. Delete Assignment and Delete Entry have nothing. So when a conflict of interest surfaces mid-round, or a panel is being rebalanced, the agent gathers the evidence and stops. It posts the assignment slug, the judges and entries it covers, the score set and rounds, whether the leaderboard already shows scores against those entries, and asks the awards manager: "Judge M. Ndlovu is assigned to 6 entries in Sustainability, and 4 of those already show scores on the Round 2 leaderboard. Their firm appears as a named partner on entry SUS-2291. Delete the assignment for that entry only, delete all 6 and reassign the category, or leave the panel and record the declaration?" A person answers, and their answer is the one on the record. Everything upstream of that, the eligibility sweep, the tagging, the reporting, runs without asking.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

44 actions

Entries

7
  • List Entries Lists entries (submissions) in the account with optional filtering by title, category, chapter, season, entrant, status and payment/review state. Results are paginated (Laravel-style) with current_page, per_page and total metadata. Use the slug of a returned entry with other entry actions.
  • Get Entry Retrieves a single entry by its slug, including entrant details, category, chapter, entry field values (with translated values) and any attachments. Use List Entries to discover entry slugs.
  • Create Entry Creates a new entry in a category on behalf of an entrant. Category, entrant, season and title are required. Field values are passed as an object keyed by field slug. Requires a write-scoped API key.
  • Update Entry Updates an existing entry identified by slug. Any subset of category, chapter, title, status, moderation status or entry field values can be supplied. Requires a write-scoped API key.
  • Delete Entry Deletes an entry by slug. Requires a write-scoped API key. There is no restore action for entries, so this is routed for sign-off.
  • Tag Entry Adds one or more tags to an entry. Tags are supplied as a comma-separated string. Requires a write-scoped API key.
  • Untag Entry Removes one or more tags from an entry. Tags are supplied as a comma-separated string. Requires a write-scoped API key.

Users

6
  • List Users Lists user accounts (entrants, judges, managers and administrators) with optional filtering by confirmation status, season and activity. Results are paginated. Use a returned user slug with Get User, Create Entry and other actions.
  • Get User Retrieves a single user account by slug or email address, including name, contact details, language, roles and preferences. Award Force resolves the identifier for either value.
  • Create User Creates a new user account. First name, last name and password are required, along with either an email address or a mobile number. Roles, preferences and custom user field values can be supplied. Requires a write-scoped API key.
  • Update User Updates an existing user identified by slug. Any subset of name, contact details, roles, preferences and custom field values can be supplied. Requires a write-scoped API key.
  • Delete User Deletes a user account by slug. Deleted users can be restored with Restore User. Requires a write-scoped API key.
  • Restore User Restores a previously deleted user account by slug. Requires a write-scoped API key.

Categories

5
  • List Categories Lists award categories with optional filtering by status, season, chapter, parent category and form. Results are paginated and include entry counts and translated names. Use a returned category slug when creating or listing entries.
  • Get Category Retrieves a single category by slug, including its translated name and description, divisions, entry limits, form and parent category.
  • Create Category Creates a new award category in a season. The translated object holds localised text keyed by field name (name is required) then by language code. Requires a write-scoped API key.
  • Update Category Updates an existing category identified by slug. Any subset of status, translated text, chapters, divisions, form and parent can be supplied. Requires a write-scoped API key.
  • Delete Category Deletes a category by slug. Requires a write-scoped API key.

Chapters

3
  • List Chapters Lists chapters (groupings such as regions or divisions) with optional filtering by status and season. Results are paginated and include the assigned managers and translated names.
  • Get Chapter Retrieves a single chapter by slug, including its translated name, season and assigned managers.
  • Create Chapter Creates a new chapter in a season. Provide localised text via the translated object (supported keys: name, image_heading) and optional chapter managers. Requires a write-scoped API key.

Seasons

2
  • List Seasons Lists the seasons (award cycles) configured in the account. Results are paginated and include each season's translated name and status. Use a returned season slug when creating entries, categories or chapters.
  • Get Season Retrieves a single season by slug, including its translated name and status.

Assignments

4
  • List Assignments Lists judging assignments that link judges to entries within a score set. Results are paginated and include the category, chapter and judging comments.
  • Get Assignment Retrieves judging assignment details for a given slug, including the entries, judges and score set involved.
  • Create Assignment Assigns entries to judges within a score set for one or more judging rounds. Score set, entries and judges are required. Requires a write-scoped API key. Routed for sign-off, because it decides who judges what.
  • Delete Assignment Deletes a judging assignment by slug. Requires a write-scoped API key. Routed for sign-off, because the judging comments carried on the assignment cannot be recreated through this connector.

Scoring

3
  • List Score Sets Lists the score sets (judging configurations) in the account. Results are paginated and include each score set's mode, season and translated name. Use a returned slug when creating assignments or fetching the leaderboard.
  • Get Score Set Retrieves a single score set by slug, including its mode, order, season and translated name.
  • Get Leaderboard Retrieves judging results ranked by score, optionally filtered by score set, entry, category, chapter or tag. Each row includes the entry, its category and chapter, and the aggregated scores. Results are paginated. This reads the ranking; scores themselves are entered by judges in Award Force.

Attachments

2
  • List Attachments Lists attachments (supporting files with metadata fields) with optional filtering by entry, category, chapter or season. Results are paginated and include attachment field values and file tokens.
  • Get Attachment Retrieves a single attachment by its file token, including the parent entry, attachment field values and file details.

Orders

3
  • List Orders Lists payment orders with optional filtering by status, season and test flag. Results are paginated and include billing details, currency, discounts and line items.
  • Get Order Retrieves a single order by slug, including billing details, currency, discount, line items and invoice number.
  • Update Order Updates an existing order identified by slug with the supplied fields (for example billing details or comments). Requires a write-scoped API key.

Review Tasks

1
  • List Review Tasks Lists review tasks (moderation and review workflow items) with optional filtering by season, reviewer, decision and review stage. Results are paginated and include the associated entry and category.

Rounds

2
  • List Rounds Lists judging rounds with optional filtering by season, form and type. Results are paginated and include each round's translated name, chapters and start/end dates.
  • Get Round Retrieves a single judging round by slug, including its translated name, season, chapters and start/end dates.

Account

1
  • Get Account Retrieves the account associated with the API key, including its name, domains, languages, owner, product tier, region and timezone.

Webhooks

5
  • List Webhooks Lists the outgoing webhook subscriptions configured in the account, with optional filtering by HTTP method, subscription event and URL. Results are paginated.
  • Get Webhook Retrieves a single webhook subscription by slug, including its name, target URL, HTTP method and subscribed events.
  • Create Webhook Creates a webhook subscription that fires when the selected events occur. Provide a name, target URL, HTTP method and the list of events to subscribe to. An optional signing key lets you validate payloads. Requires a write-scoped API key. The subscription posts to the endpoint you name; it does not create a FlowRunner trigger.
  • Update Webhook Updates an existing webhook subscription identified by slug. Any subset of name, URL, HTTP method, events and signing key can be supplied. Requires a write-scoped API key.
  • Delete Webhook Deletes a webhook subscription by slug. Requires a write-scoped API key.

Frequently Asked Questions

What can FlowRunner do with Award Force?

FlowRunner agents can run List Entries, Get Entry, and Create Entry in Award Force, plus 41 more actions.

Does connecting Award Force to FlowRunner require OAuth?

No. Award Force connects to FlowRunner with an API key, no OAuth flow required.

Can Award Force trigger a FlowRunner workflow automatically?

Award Force doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Award Force

$100 in credits. No card required. Connect in minutes.