Create playtable field
Add a column to a playtable: the tool that shapes a table. category is derived from the type prefix, never sent.
Patterns. Find people (a company grid): type action_find_people with payload.prompt saying who to find at each company (1 credit per company searched, a miss free); switch config.auto_run on (its default condition is a company with no people yet) so a company that lands later is searched by itself, and a playtable run searches the companies already there. Add as column: a scalar whose payload.template is one lone variable such as {{record.enrich.company.employees}}; existing rows backfill free, every future run re-derives it; never touch the action field for this. Composed text: a template with {{people.first_name}} or {{company.name}} (catalog attributes) and record.<slug> (a column of this tab), each refused unless it exists. action_waterfall: config.preset_sid (a gtm-api preset) or hand-built payload.steps, never both.
Formulas and templates form dependency edges; a cycle rolls the save back with 422 and context.cycle_path. Idempotent on (playtable_sid, slug): a duplicate answers already_exists true with the existing row (check item.type). Nothing paid runs on create (a playtable run, estimate first, or auto_run does); a scalar formula backfill is free. At most 100 live columns per object_type: the 101st is 422 (context.limit).
Contract:
- MCP tool create_playtable_field, registry package mcp.playtables/playtable_fields, mount playtables.columns.
- Operation create, response envelope create.
- Flags: none.
Request
- Base URLhttps://beta.getsales.io/playtables/v1
- AuthHTTP bearer and API key in header Team-SID
Request body
Response
create success envelope.
Changes
No recorded changes to this operation across all 1 revision of this API.