Skip to content

getaero-io/gtm-eng-skills / skills/deepline-gtm

deepline-gtm

Unverified

GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,buyercaddy,cbinsights,clay,clickhouse,close,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,deepseek,discolike,dnb,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,kickbox,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meerapi,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,particle,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,….

FileKindSize
SKILL.mdskill md15.9 KB
claude-deepline-statusline.mjsexecutablescript25.0 KB
prompts.jsonconfig297.9 KB
provider-playbooks/adyntel.mdmarkdown1.2 KB
provider-playbooks/affinity.mdmarkdown825 B
provider-playbooks/ai-ark.mdmarkdown10.6 KB
provider-playbooks/akta.mdmarkdown1.5 KB
provider-playbooks/allegrow.mdmarkdown4.6 KB
provider-playbooks/amplemarket.mdmarkdown2.8 KB
provider-playbooks/apify.mdmarkdown1.8 KB
provider-playbooks/attention.mdmarkdown449 B
provider-playbooks/attio.mdmarkdown5.6 KB
provider-playbooks/aviato.mdmarkdown756 B
provider-playbooks/bettercontact.mdmarkdown1.7 KB
provider-playbooks/bigquery.mdmarkdown1019 B
provider-playbooks/bloomberry.mdmarkdown935 B
provider-playbooks/bluesky.mdmarkdown139 B
provider-playbooks/bounceban.mdmarkdown1.6 KB
provider-playbooks/brave.mdmarkdown422 B
provider-playbooks/browserbase.mdmarkdown1.0 KB
provider-playbooks/builtwith.mdmarkdown1.0 KB
provider-playbooks/buyercaddy.mdmarkdown2.3 KB
provider-playbooks/cbinsights.mdmarkdown436 B
provider-playbooks/clay.mdmarkdown875 B
provider-playbooks/clickhouse.mdmarkdown1.1 KB
provider-playbooks/close.mdmarkdown2.6 KB
provider-playbooks/cloudflare.mdmarkdown2.3 KB
provider-playbooks/contactout.mdmarkdown8.3 KB
provider-playbooks/contextdev.mdmarkdown582 B
provider-playbooks/crunchbase.mdmarkdown742 B
provider-playbooks/crustdata-v2.mdmarkdown490 B
provider-playbooks/crustdata-v3.mdmarkdown8.4 KB
provider-playbooks/crustdata.mdmarkdown6.8 KB
provider-playbooks/databricks.mdmarkdown3.5 KB
provider-playbooks/dataforseo.mdmarkdown950 B
provider-playbooks/datagma.mdmarkdown6.0 KB
provider-playbooks/dealroom.mdmarkdown632 B
provider-playbooks/deepline-ip-to-company.mdmarkdown480 B
provider-playbooks/deepline-native-osint.mdmarkdown1.5 KB
provider-playbooks/deepline-native.mdmarkdown25.1 KB
provider-playbooks/deeplineagent.mdmarkdown2.7 KB
provider-playbooks/deepseek.mdmarkdown1.2 KB
provider-playbooks/discolike.mdmarkdown6.2 KB
provider-playbooks/dnb.mdmarkdown1.4 KB
provider-playbooks/dropleads.mdmarkdown10.2 KB
provider-playbooks/edges.mdmarkdown875 B
provider-playbooks/emailbison.mdmarkdown634 B
provider-playbooks/emailguard.mdmarkdown243 B
provider-playbooks/enformion.mdmarkdown9.3 KB
provider-playbooks/enigma.mdmarkdown1.7 KB
provider-playbooks/exa.mdmarkdown1.4 KB
provider-playbooks/file-transport.mdmarkdown739 B
provider-playbooks/findymail.mdmarkdown880 B
provider-playbooks/firecrawl.mdmarkdown2.4 KB
provider-playbooks/fireflies.mdmarkdown988 B
provider-playbooks/firmable.mdmarkdown1.3 KB
provider-playbooks/forager.mdmarkdown2.3 KB
provider-playbooks/fullenrich.mdmarkdown2.1 KB
provider-playbooks/fundable.mdmarkdown2.0 KB
provider-playbooks/generic-http.mdmarkdown348 B
provider-playbooks/getleads.mdmarkdown2.2 KB
provider-playbooks/gong.mdmarkdown488 B
provider-playbooks/google-ads-audiences.mdmarkdown2.0 KB
provider-playbooks/google-calendar-availability.mdmarkdown1.6 KB
provider-playbooks/google-calendar.mdmarkdown1.1 KB
provider-playbooks/google-sheets.mdmarkdown842 B
provider-playbooks/google-workspace.mdmarkdown2.1 KB
provider-playbooks/govfiles.mdmarkdown1.8 KB
provider-playbooks/grain.mdmarkdown1.0 KB
provider-playbooks/hackernews.mdmarkdown208 B
provider-playbooks/harvestapi.mdmarkdown3.5 KB
provider-playbooks/heyreach.mdmarkdown1.6 KB
provider-playbooks/hubspot.mdmarkdown3.3 KB
provider-playbooks/hunter.mdmarkdown849 B
provider-playbooks/icypeas.mdmarkdown1.8 KB
provider-playbooks/instantly.mdmarkdown1.6 KB
provider-playbooks/integration-operation.mdmarkdown704 B
provider-playbooks/intercom.mdmarkdown275 B
provider-playbooks/ipqs.mdmarkdown1.7 KB
provider-playbooks/kaspr.mdmarkdown822 B
provider-playbooks/kernel.mdmarkdown875 B
provider-playbooks/leadmagic.mdmarkdown5.3 KB
provider-playbooks/lemlist.mdmarkdown7.5 KB
provider-playbooks/limadata.mdmarkdown636 B
provider-playbooks/linkedin-ads-audiences.mdmarkdown629 B
provider-playbooks/luma.mdmarkdown3.2 KB
provider-playbooks/lusha.mdmarkdown3.5 KB
provider-playbooks/meerapi.mdmarkdown1.2 KB
provider-playbooks/meta-audiences.mdmarkdown4.8 KB
provider-playbooks/millionverifier.mdmarkdown618 B
provider-playbooks/nooks.mdmarkdown1.0 KB
provider-playbooks/notion.mdmarkdown724 B
provider-playbooks/openmart.mdmarkdown2.3 KB
provider-playbooks/opensosdata.mdmarkdown4.0 KB
provider-playbooks/openwebninja.mdmarkdown315 B
provider-playbooks/outreach.mdmarkdown2.6 KB
provider-playbooks/parallel.mdmarkdown4.4 KB
provider-playbooks/particle.mdmarkdown2.0 KB
provider-playbooks/peopledatalabs.mdmarkdown4.5 KB
provider-playbooks/pipedrive.mdmarkdown582 B
provider-playbooks/pitchbook.mdmarkdown606 B
provider-playbooks/podscan.mdmarkdown2.7 KB
provider-playbooks/polymarket.mdmarkdown2.2 KB
provider-playbooks/postgres.mdmarkdown553 B
provider-playbooks/predictleads.mdmarkdown622 B
provider-playbooks/prospeo.mdmarkdown2.4 KB
provider-playbooks/quickenrich.mdmarkdown595 B
provider-playbooks/rapidapi.mdmarkdown2.5 KB
provider-playbooks/rb2b.mdmarkdown247 B
provider-playbooks/redshift.mdmarkdown763 B
provider-playbooks/reo-write.mdmarkdown1.6 KB
provider-playbooks/reo.mdmarkdown2.0 KB
provider-playbooks/resend.mdmarkdown3.6 KB
provider-playbooks/salesforce.mdmarkdown3.6 KB
provider-playbooks/salesforge.mdmarkdown274 B
provider-playbooks/salesloft.mdmarkdown1.0 KB
provider-playbooks/scrapecreators.mdmarkdown3.4 KB
provider-playbooks/searchbug.mdmarkdown637 B
provider-playbooks/sec-edgar.mdmarkdown1.6 KB
provider-playbooks/sentrion.mdmarkdown737 B
provider-playbooks/serper.mdmarkdown1011 B
provider-playbooks/slack.mdmarkdown21.1 KB
provider-playbooks/smartleads.mdmarkdown11.8 KB
provider-playbooks/snitcher.mdmarkdown302 B
provider-playbooks/snowflake.mdmarkdown768 B
provider-playbooks/socrata.mdmarkdown3.2 KB
provider-playbooks/sumble.mdmarkdown1.3 KB
provider-playbooks/tamradar.mdmarkdown1.4 KB
provider-playbooks/test-unhinted.mdmarkdown505 B
provider-playbooks/test.mdmarkdown254 B
provider-playbooks/theirstack.mdmarkdown4.4 KB
provider-playbooks/theswarm.mdmarkdown1.4 KB
provider-playbooks/treg.mdmarkdown1.5 KB
provider-playbooks/trestle.mdmarkdown3.7 KB
provider-playbooks/trykitt.mdmarkdown862 B
provider-playbooks/twitterapi.mdmarkdown3.6 KB
provider-playbooks/unipile.mdmarkdown4.8 KB
provider-playbooks/upcell.mdmarkdown715 B
provider-playbooks/vector.mdmarkdown257 B
provider-playbooks/versium.mdmarkdown690 B
provider-playbooks/wiza.mdmarkdown2.0 KB
provider-playbooks/wizleads.mdmarkdown1.1 KB
provider-playbooks/zerobounce.mdmarkdown1.3 KB
provider-playbooks/zoho-crm.mdmarkdown630 B
provider-playbooks/zoominfo.mdmarkdown1.2 KB
recipes/account-orgchart.mdmarkdown35.6 KB
recipes/build-tam.mdmarkdown3.7 KB
recipes/clay-to-deepline.mdmarkdown26.8 KB
recipes/deepline-monitors.mdmarkdown32.5 KB
recipes/developer-signals.mdmarkdown14.7 KB
recipes/find-qualified-titles.mdmarkdown5.2 KB
recipes/portfolio-prospecting.mdmarkdown3.6 KB
recipes/small-business-prospecting.mdmarkdown3.0 KB
references/clay-action-mappings.mdmarkdown40.0 KB
references/clay-api-surface.mdmarkdown18.6 KB
references/clay-extraction.mdmarkdown16.2 KB
references/industry-radars.mdmarkdown3.3 KB
references/monitor-contract-reference.mdmarkdown25.9 KB
references/monitor-operations.mdmarkdown12.4 KB
references/monitor-sdk.mdmarkdown3.2 KB
references/run-events.mdmarkdown14.3 KB
scripts/clay-extract-bookmarklet.jsscript10.5 KB
scripts/clay-extract-bookmarklet.url.txtmarkdown8.2 KB
scripts/clay-extract.pyscript17.9 KB
scripts/clay-har-miner.pyscript5.8 KB
scripts/clay-to-deepline.mjsscript134.1 KB
scripts/contact-accuracy-audit.pyscript8.9 KB
scripts/fixtures_contact_accuracy_audit.jsonconfig5.5 KB
scripts/fixtures_current_role.jsonconfig10.3 KB
scripts/flatten-search-contact-persons.pyscript3.3 KB
scripts/select-current-role.pyscript12.2 KB
scripts/validate-emails.pyexecutablescript2.0 KB
skill-metadata.jsonconfig2.2 KB
writing-outreach.mdmarkdown14.1 KB

references/clay-api-surface.md

View on GitHub
# Clay internal API surface

Clay has no public API for table config. Everything below is the **internal v3 API** the web app itself calls, recovered from 82MB of recorded HAR traffic across 5 workspaces and re-verified live. Host is `https://api.clay.com`. Auth is the browser session cookie, so `credentials: 'include'` from an `app.clay.com` tab is all you need - never copy the cookie into a script.

Treat this as observed behavior, not a contract. Clay can change it without notice. Re-run the miner (below) when something breaks.

## The three you almost always want

| Need                                                | Endpoint                                                            |
| --------------------------------------------------- | ------------------------------------------------------------------- |
| Every action Clay offers, with input/output schemas | `GET /v3/actions?workspaceId={WS}`                                  |
| A workbook's child tables                           | `GET /v3/workbooks/{WORKBOOK_ID}/tables`                            |
| A workbook's dependency graph                       | `GET /v3/{WS}/workbooks/{WORKBOOK_ID}/overview` -> `{nodes, edges}` |

`/v3/actions` is ~25MB and returns `{actions: [...]}` - 1398 entries in the workspace it was captured from. Each carries `key`, `displayName`, `package`, `categories`, `description`, `inputParameterSchema`, `outputParameterSchema`, `auth`. This is the authoritative answer to "what does Clay action `X` actually take", and it is how you map an unfamiliar `actionKey` instead of guessing.

`/overview` returns the workbook's real node/edge graph. Prefer it over hand-deriving a dependency diagram from field configs.

## Tables and records

| Method | Path                                                     | Query                                 | Notes                                                                                                                                       |
| ------ | -------------------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `GET`  | `/v3/tables/{TABLE_ID}`                                  | `includeExtraData`, `extraDataViewId` | Config. Fields are at `.table.fields`, NOT `.fields`. `firstViewId` is at `.table.firstViewId`.                                             |
| `GET`  | `/v3/tables/{TABLE_ID}/count`                            | -                                     | `{tableTotalRecordsCount}`. True size.                                                                                                      |
| `GET`  | `/v3/tables/{TABLE_ID}/views/{VIEW_ID}/table-schema-v2`  | -                                     | `{tableSchema, exampleRecords}`. exampleRecords carry RENDERED formula/action values - richest prompt source. Capped by Clay (~25-55 rows). |
| `GET`  | `/v3/tables/{TABLE_ID}/views/{VIEW_ID}/records/ids`      | -                                     | `{results: [r_xxx]}`. All ids, no pagination.                                                                                               |
| `POST` | `/v3/tables/{TABLE_ID}/bulk-fetch-records`               | -                                     | Body `{recordIds: [...], includeExternalContentFieldIds: []}`. Returns `{results}`. Batch ~50.                                              |
| `GET`  | `/v3/tables/{TABLE_ID}/fieldrun`                         | -                                     | `{fieldIds}` - which fields have run.                                                                                                       |
| `GET`  | `/v3/workspaces/{WS}/tables/{TABLE_ID}/fields/runstatus` | -                                     | `{statusCountsByField}` - per-field run state. Better than inferring "did this column fire" from cells.                                     |
| `GET`  | `/v3/tables/{TABLE_ID}/has-overflow-csvs/`               | -                                     | Whether the table spilled to CSV.                                                                                                           |

## Workbooks

| Method | Path                                        | Notes                                                                                                     |
| ------ | ------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| `GET`  | `/v3/workbooks/{WORKBOOK_ID}/tables`        | Array of child tables (`id`, `name`, `type`, `workbookId`). The entry point for a whole-workbook extract. |
| `GET`  | `/v3/{WS}/workbooks/{WORKBOOK_ID}`          | Workbook metadata.                                                                                        |
| `GET`  | `/v3/{WS}/workbooks/{WORKBOOK_ID}/overview` | `{nodes, edges}` dependency graph.                                                                        |

Note the inconsistency: `/tables` has no workspace segment, the other two do. That is Clay's shape, not a typo.

## Sources

| Method | Path                           | Query     | Notes                                                                                             |
| ------ | ------------------------------ | --------- | ------------------------------------------------------------------------------------------------- |
| `GET`  | `/v3/sources`                  | `tableId` | Source config for a table. Recovers filter criteria that a table-config extract does NOT include. |
| `GET`  | `/v3/sources/{SOURCE_ID}`      | -         | One source.                                                                                       |
| `GET`  | `/v3/sources/{SOURCE_ID}/runs` | `limit`   | Run history.                                                                                      |

If a migration needs to know "what population did this table source", `/v3/sources?tableId=` is the only place that answers it.

## Actions and integrations

| Method | Path                                                    | Query                        | Notes                                                                             |
| ------ | ------------------------------------------------------- | ---------------------------- | --------------------------------------------------------------------------------- |
| `GET`  | `/v3/actions`                                           | `workspaceId`                | Full catalog, ~25MB.                                                              |
| `POST` | `/v3/actions/dynamicFields`                             | -                            | Resolves fields that depend on a connected account (e.g. HubSpot property lists). |
| `GET`  | `/v3/app-accounts/types`                                | -                            | Every integration type.                                                           |
| `GET`  | `/v3/app-accounts/type/{TYPE}`                          | -                            | One integration type.                                                             |
| `GET`  | `/v3/workspaces/{WS}/app-accounts`                      | -                            | Connected accounts.                                                               |
| `GET`  | `/v3/workspaces/{WS}/app-accounts/accounts/type/{TYPE}` | `resourceId`, `resourceType` | Connected accounts of one type.                                                   |

## Workspace, account, billing

| Method | Path                                                    | Notes                                                                                                          |
| ------ | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| `GET`  | `/v3/me`                                                | Current user.                                                                                                  |
| `GET`  | `/v3/my-workspaces`                                     | Workspaces you can reach.                                                                                      |
| `GET`  | `/v3/workspaces/{WS}`                                   | Workspace metadata.                                                                                            |
| `GET`  | `/v3/workspaces/{WS}/users`                             | Members.                                                                                                       |
| `GET`  | `/v3/workspaces/{WS}/permissions`                       | Your permissions.                                                                                              |
| `GET`  | `/v3/workspaces/{WS}/subroutines`                       | Saved subroutines.                                                                                             |
| `GET`  | `/v3/workspaces/{WS}/trigger-definitions-with-schedule` | Scheduled triggers. Use this to spot tables that need a play with a `cron` binding rather than a plain enrich. |
| `GET`  | `/v3/workspaces/{WS}/resources/{RESOURCE_ID}`           | Resource metadata (`resourceType` query).                                                                      |
| `GET`  | `/v3/billingplans/{ID}`                                 | Plan.                                                                                                          |
| `GET`  | `/v3/subscriptions/{ID}`                                | Subscription.                                                                                                  |
| `GET`  | `/v3/credit-accrual`                                    | Credit accrual.                                                                                                |
| `GET`  | `/v3/model-pricing/{WS}/base-costs`                     | Per-model base costs.                                                                                          |
| `GET`  | `/v3/clayback-analytics`                                | Usage analytics.                                                                                               |

## CRM read and write

`clay-action-mappings.md` covers enrichment actions. CRM actions live here. Clay ships 27 HubSpot actions plus a Salesforce package; these are the keys that show up in real tables. Confirm the Deepline side with `deepline describe <tool_id>` before writing a pass.

| Clay action                                          | Deepline tool                          |
| ---------------------------------------------------- | -------------------------------------- |
| `hubspot-lookup-object`, `hubspot-lookup-contact-v2` | `hubspot_search_objects`               |
| `hubspot-create-object`, `hubspot-create-company`    | `hubspot_create_object`                |
| `hubspot-update-object`                              | `hubspot_update_object`                |
| `hubspot-get-properties`                             | `hubspot_fetch_properties`             |
| `hubspot-find-owner`                                 | `hubspot_list_owners`                  |
| `hubspot-retrieve-associations`                      | `hubspot_batch_read_associations`      |
| `hubspot-enroll-contact`                             | Sequencer step, not an enrich column   |
| `hubspot-crm-objects-source`                         | Seed the CSV from HubSpot, then enrich |

`hubspot-lookup-object` inputs are `objectTypeId`, `fields`, `removeBlankValues`, `limit`. A lookup returning a list interpolates by full path: `{{hs_lookup.results[0].id}}`.

### Clay-native table actions

**`lookup-row-in-other-table`** - inputs `tableId`, `fields|targetColumn`, `fields|filterOperator`, `fields|rowValue`. Not a provider call. Export the referenced table to CSV and join with a native Play callback, or query `customer_db` if the data already lives there.

**`route-row`** ("Send table data", Clay Labs) - inputs `type`, `tableId`, `rowData`, `nestedData`, `listData`, `isUpsertDisabled`. Writes rows into a different table, so it is not replicable as an enrich column. Produce a filtered output CSV per destination, or model the fan-out as a play.

## Map by job, not by provider name

287 distinct `actionKey` values show up across real Clay tables, but they collapse into about ten jobs. Clay names an action per provider (19 different phone finders, 15 work-email finders); Deepline expresses the same job as one waterfall that tries providers in order and stops when it finds a value. So do NOT hunt for a one-to-one tool per Clay action. Identify the job, use the waterfall, and let it handle provider order.

| Clay actions matching                                                                                                               | Job                  | Deepline                                                                                                                |
| ----------------------------------------------------------------------------------------------------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| anything matching `phone` or `mobile` - `*-find-phone`, `*-find-mobile`, `*-find-phone-number`, `clearout-validate-phone` (21 keys) | mobile phone         | `prebuilt/person-to-phone`                                                                                              |
| `*-find-work-email`, `find-email-v2`, `icypeas-find-email-v2` (15 keys)                                                             | work email           | `prebuilt/name-and-domain-to-email-waterfall`, or `prebuilt/person-linkedin-to-email` when you have a LinkedIn URL      |
| `*-find-personal-email`, `*-personal-email-from-linkedin` (14 keys)                                                                 | personal email       | `prebuilt/personal-email`                                                                                               |
| `validate-email`, `*-verify-email`, `*-validate-email` (14 keys)                                                                    | email validation     | `leadmagic_email_validation` or `zerobounce_validate`. Accept `valid`, `valid_catch_all`, `catch_all`; reject `unknown` |
| `*-find-linkedin-profile`, `contactout-social-url-from-email` (10 keys)                                                             | resolve LinkedIn URL | Discover an available people-search or public-search API; validate identity against authorized data                     |
| `enrich-person`, `enrich-person-with-mixrank-v2`, `*-enrich-person` (10 keys)                                                       | person enrichment    | `leadmagic_profile_search` then `crustdata_v3_person_enrich`                                                            |
| `enrich-company`, `*-enrich-company`, `crunchbase-enrich-*` (22 keys)                                                               | company enrichment   | `prospeo_enrich_company` or `crustdata_v3_company_search`                                                               |
| `use-ai`, claygent variants                                                                                                         | AI generation        | `deeplineagent` with a `jsonSchema`                                                                                     |
| `find-lists-of-*-with-mixrank`, `search-person`                                                                                     | sourcing a new list  | `crustdata_v3_company_search` or `prebuilt/company-to-contact`                                                          |
| `add-lead-to-campaign`, sequencer keys                                                                                              | campaign push        | `instantly_add_to_campaign`, `smartlead_push_to_campaign`                                                               |

Keys ending `-validate-auth` are Clay's connection health checks. They are not data columns - ignore them during migration.

**Read the column's config, not just its name.** A generic key like `enrich-person` or `*-enrich-person` is often wired as a phone or email finder: check `typeSettings.inputsBinding` for a flag such as `requirePhone`, and check what downstream columns actually consume. Map by what the column produces in that table, not by what its key is called. Clay also chains finders with `conditionalRunFormulaText` so each fires only when the previous missed - that is a waterfall, and it becomes ONE Deepline waterfall play, not one pass per provider.

Expect providers with no Deepline equivalent (surfe, zeliq, smarte, lyne, bytemine, clearout all lack one). That is fine and is the reason to map by job: the waterfall covers the outcome with the providers Deepline does have.

Those patterns cover about 85% of real-table action usage. The rest is genuine long tail - funding data (`intellizence-`, `harmonic-`, `dealroom-`, `cb-insights-`), web/traffic (`semrush-`, `similarweb-`, `capterra-scrape`), and one-off scrapers. For those, pull the schema from the catalog (below), then `deepline search "<input you have -> result you need>"`. If nothing fits, `deeplineagent` with a `jsonSchema` is the fallback, and `generic_http_request` covers a provider Deepline does not wrap.

## Mapping an unknown Clay action

When a table uses an `actionKey` that `clay-action-mappings.md` does not cover, do NOT guess. Pull the catalog and read its schema:

```bash
# from an app.clay.com tab, via the bookmarklet console or javascript_tool
fetch('https://api.clay.com/v3/actions?workspaceId=' + WS, {credentials:'include'})
  .then(r => r.json())
  .then(d => d.actions.filter(a => a.key === 'hubspot-lookup-object')
                      .map(a => ({key:a.key, inputs:a.inputParameterSchema})));
```

Then find the Deepline equivalent with `deepline search "<input you have -> result you need>"` and confirm with `deepline describe <tool_id>`.

## Re-mining when Clay changes

The endpoint list above came from HAR captures. To regenerate after a Clay update:

1. In Chrome DevTools -> Network, record while you exercise the Clay UI (open a workbook, a table, run a column, open the action picker).
2. Right-click -> "Save all as HAR with content".
3. Run the miner in `scripts/clay-har-miner.py` against the HAR. It normalizes ids into placeholders and emits one row per distinct route with methods, statuses, query params, and payload shapes.

Large responses (`/v3/actions` in particular) are often recorded without bodies because of DevTools size limits. Fetch those live from a logged-in tab instead of expecting them in the HAR.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall