Sumble: Get Organization Signals

Get a company’s signals, such as hiring, job changes and technology mentions, optionally for specific technologies.

Tool ID: sumble_get_organization_signals

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'sumble_get_organization_signals',
  {
    "organization_id": 123
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute sumble_get_organization_signals --input '{
  "organization_id": 123
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "id": "123e4567-e89b-42d3-a456-426614174000",
    "signals": [
      {
        "title": "VP of Engineering",
        "date": "2026-01-15T12:00:00Z",
        "display_type": "example"
      }
    ]
  }
}

Use deepline describe sumble_get_organization_signals --json for the latest machine-readable contract.

Input reference

Get organization signals

Name	Type	Required	Default	Details
`payload.organization_id`	`integer`	Yes	—	—
`payload.technology_slugs`	`array`	No	—	Technology slugs to filter signals by. Repeat this query parameter to filter by multiple technologies. Use POST /technologies/lookup to resolve technology names, slugs, or aliases to canonical slugs. Use POST /technologies/find to search for matching technologies.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.id`	`string`	Yes	—	Format: `uuid`.
`result.data.signals`	`array`	Yes	—	—
`result.data.signals[].signal_id`	`integer \| null`	No	—	—
`result.data.signals[].title`	`string`	Yes	—	—
`result.data.signals[].subtitle`	`string \| null`	No	—	—
`result.data.signals[].explanation`	`string \| null`	No	—	—
`result.data.signals[].sales_angle`	`string \| null`	No	—	—
`result.data.signals[].date`	`string`	Yes	—	Format: `date-time`.
`result.data.signals[].sumble_url`	`string \| null`	No	—	—
`result.data.signals[].display_type`	`string`	Yes	—	—
`result.data.signals[].type`	`string \| null`	No	—	—
`result.data.signals[].matched_technologies`	`array \| null`	No	—	—
`result.data.signals[].matched_technologies[].name`	`string`	Yes	—	—
`result.data.signals[].matched_technologies[].slug`	`string`	Yes	—	—
`result.data.signals[].matched_technologies[].label`	`string \| null`	No	—	—
`result.data.signals[].organization_name`	`string \| null`	No	—	—
`result.data.signals[].organization_id`	`integer \| null`	No	—	—
`result.data.signals[].job_post_id`	`integer \| null`	No	—	—
`result.data.signals[].person_id`	`integer \| null`	No	—	—
`result.data.signals[].linkedin_url`	`string \| null`	No	—	—
`result.data.signals[].location`	`string \| null`	No	—	—
`result.data.signals[].job_function`	`string \| null`	No	—	—
`result.data.signals[].priority`	`string \| null`	No	—	—
`result.data.signals[].suggested_contacts`	`object \| null`	No	—	—
`result.data.signals[].suggested_contacts.people`	`array`	Yes	—	—
`result.data.signals[].suggested_contacts.people[].person_id`	`integer \| null`	No	—	—
`result.data.signals[].suggested_contacts.people[].name`	`string \| null`	No	—	—
`result.data.signals[].suggested_contacts.people[].title`	`string \| null`	No	—	—
`result.data.signals[].suggested_contacts.people[].linkedin_url`	`string \| null`	No	—	—
`result.data.signals[].suggested_contacts.people[].score`	`number \| null`	No	—	—
`result.data.signals[].suggested_contacts.sumble_url`	`string \| null`	No	—	—
`result.data.signals[].account_status`	`"is_customer" \| "is_in_crm" \| "is_not_in_crm"`	No	—	CRM relationship between the signal’s organization and the calling account: ‘is_customer’ (a customer account in the calling account’s CRM), ‘is_in_crm’ (tracked in CRM but not a customer), or ‘is_not_in_crm’ (no CRM record). Only populated when the calling account has a linked CRM seat (Salesforce or HubSpot). omitted otherwise, even when requested. Allowed: `is_customer`, `is_in_crm`, `is_not_in_crm`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation