FlowRunner
PricingContact
Theme
Start Free

Read public Steam player and game data through Valve's Steam Web API. Agents resolve vanity URLs to SteamIDs, pull player profiles and friend lists, report owned and recently played games, track achievement progress, and fetch game news.

9 actions API key available
Steam website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A community member submits their Steam profile name through the sign-up form
Resolve Vanity URL converts the username into a 64-bit SteamID
A success=42 response means no match, and the submission routes back for correction instead of writing a bad ID
Get Player Summaries pulls the public profile: display name, avatar, country, persona state
Get Recently Played Games and Get Owned Games build the player's activity picture
The enriched member record lands in the community database and the mod channel gets a summary
A community manager reviews members flagged by the enrichment, private profiles, mismatched names, before any community role or reward is granted on the data

What This Integration Enables

Valve's Steam Web API is a read-only window into the largest PC gaming platform, and the teams who need it, community managers, esports organizers, gaming-adjacent brands, researchers, mostly interact with it through manual profile checks. This connector automates the window. FlowRunner agents resolve vanity URLs to SteamIDs, batch profile lookups up to 100 players per call, pull owned libraries and playtime, track achievement progress against global rarity, and watch game news feeds. - Enrich member and customer records from a Steam username alone - Report on owned libraries, total playtime, and two-week activity - Track achievement progress per player per game, with global unlock percentages for rarity context - Syndicate game news and update announcements by App ID - Cross-reference public friend lists with player summaries - Reach any other Steam Web API method through the Call Steam Method escape hatch Everything here reads public data, so the [human-in-the-loop](/concepts/human-in-the-loop) judgment lands not on protecting Steam but on what your workflow does with data about real people.

Without FlowRunner

Player data is copy-pasted from profiles Community managers open steamcommunity.com pages one by one to check who plays what
Game news is monitored by refresh Update announcements for tracked titles get noticed whenever someone happens to look
Engagement reporting is anecdotal Which games the community actually plays is a guess assembled from chat mentions

With FlowRunner

Profiles enrich themselves Vanity names resolve to SteamIDs and profiles, libraries, and playtime attach automatically
Game news arrives as an event New announcements for tracked App IDs post to the community channels within the polling window
Engagement is measured Playtime, achievement progress, and recently played data aggregate into real reports

Use Case Scenarios

Community onboarding that verifies itself

New members submit their profile name; the agent resolves it, pulls Get Player Summaries and Get Recently Played Games, and writes the enriched record to [Google Sheets](/integrations/google-sheets). Members whose profiles are private or whose activity does not match the community's game get flagged for a human look rather than auto-rejected, because a privacy setting is not a character flaw.

The game-update watch that never sleeps

On a polling schedule, Get News For App checks the tracked titles. New items post to [Discord](/integrations/discord) with title, link, and a truncated body, and a parallel note goes to [Slack](/integrations/slack) for the internal team. Patch announcements that affect a tournament or a content calendar arrive as events, not as things someone eventually saw on the store page.

Achievement race reporting with rarity context

For a community event, the agent pulls Get Player Achievements for each registered player against the event's App ID, joins the results with Get Global Achievement Percentages so each unlock carries its rarity, and publishes the leaderboard. Standings update on a schedule all weekend. What used to be a volunteer manually checking profiles becomes a report that runs itself, with the organizer reviewing only disputes.

Human-in-Loop Highlight

Nothing in this connector deletes or spends: it is read-only against public data. The gravity sits in Call Steam Method and in what happens downstream of the reads. The escape hatch can reach any Steam Web API interface, which means a workflow author can wire up endpoints beyond the vetted set, so new Call Steam Method usages get a human review of what the endpoint returns and where the workflow sends it before running unattended. The subtler gate is decisions made on player data: a community workflow that grants roles, prizes, or access based on profile and playtime data will meet private profiles, resolved-name mismatches, and API hiccups, and treating those as automatic disqualification punishes people for privacy settings. Ambiguous cases queue for a community manager with the raw responses attached. The agent gathers evidence at machine speed; membership judgments about real people stay human.

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

9 actions

Players

3
  • Get Player Summaries Retrieves public profile data for up to 100 SteamIDs per call: display name, avatar, profile URL, persona state, and, when public, current game, country, and account creation time.
  • Resolve Vanity URL Resolves a custom profile username into its 64-bit SteamID, returning success=1 with the ID or success=42 for no match. The first step whenever only a username is known.
  • Get Friend List Retrieves a user's public friend list with each friend's SteamID, relationship, and friendship timestamp, ready to join with Get Player Summaries.

Games

5
  • Get Owned Games Retrieves a user's owned games with per-game total playtime in minutes, optionally with names and icons, and optionally limited to games actually played. Requires public game details.
  • Get Player Achievements Retrieves a player's achievement progress for a specific App ID: API name, unlocked status, and unlock time, with optional localized display names.
  • Get Recently Played Games Retrieves the games a user played in the last two weeks with recent and total playtime. The activity signal behind engagement reporting.
  • Get News For App Retrieves the latest news items for a game by App ID with title, author, feed, URL, publish date, and content, with count and body-length controls. Requires no player permissions.
  • Get Global Achievement Percentages Retrieves every achievement's global unlock rate for a game, the rarity context that makes achievement reporting meaningful.

Advanced

1
  • Call Steam Method Escape hatch for any Steam Web API interface and method not covered above: specify interface, method, version, and query parameters, with the API key and JSON format appended automatically. New usages earn a human review before running unattended.

Frequently Asked Questions

What can FlowRunner do with Steam?

FlowRunner agents can run Get Player Summaries, Resolve Vanity URL, and Get Friend List in Steam, plus 6 more actions.

Does connecting Steam to FlowRunner require OAuth?

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

Can Steam trigger a FlowRunner workflow automatically?

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

Start building with Steam

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