Fundable: Get Alerts

Get the funding deals that matched your saved Fundable alerts within a date range, newest first.

Tool ID: fundable_get_alerts

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(
  'fundable_get_alerts',
  {
    "alert_ids": "alert_123",
    "start_date": "2026-01-15T12:00:00Z",
    "end_date": "2026-01-15T12:00:00Z"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute fundable_get_alerts --input '{
  "alert_ids": "alert_123",
  "start_date": "2026-01-15T12:00:00Z",
  "end_date": "2026-01-15T12:00:00Z"
}' --json

Example response

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

{
  "data": {
    "success": true,
    "data": {},
    "meta": {
      "page": 123,
      "page_size": 123
    }
  }
}

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

Input reference

Retrieve saved alert data including all deals that matched the alert criteria within the specified date range. Results include a flattened array of deals sorted by date (newest first) with duplicates removed. Available on Pro+ and Enterprise plans. This endpoint does not consume credits. Multiple Alerts Support: - Query multiple alerts in a single request (up to 10) - Each alert returns its own flattened deals array - Different alerts can have different frequencies (e.g., one daily, one weekly) - Successful requests report credits_used: 0, regardless of deal count Important Notes: - All alert_ids must belong to alerts you have access to - Deals are flattened from all time periods and sorted by date DESC (newest first) - Duplicate deals are automatically removed - Each deal includes AI-generated reasoning for why it matched the alert criteria - Deal structure is simplified with See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.alert_ids`	`string`	Yes	—	Comma-separated list of alert UUIDs (up to 10 alerts per request). All alerts must be associated with your API key’s account. Example: “uuid1,uuid2,uuid3”
`payload.start_date`	`string`	Yes	—	Start date for the alert data range (ISO 8601 format). Results will include deals from this date onwards. Format: `date-time`.
`payload.end_date`	`string`	Yes	—	End date for the alert data range (ISO 8601 format). Results will include deals up to and including this date. Note: All dates are processed in UTC timezone. Deals are grouped into time periods based on UTC date boundaries. Format: `date-time`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.success`	`boolean`	Yes	—	—
`result.data.data`	`object`	Yes	—	—
`result.data.data.alerts`	`array`	No	—	Array of alert configurations with their timeline data
`result.data.data.alerts[].alertId`	`string`	Yes	—	Unique identifier for the alert configuration Format: `uuid`.
`result.data.data.alerts[].alertName`	`string`	Yes	—	Name of the alert configuration
`result.data.data.alerts[].alertFrequency`	`"DAILY" \| "WEEKLY" \| "BIWEEKLY" \| "MONTHLY"`	Yes	—	Frequency setting of the alert Allowed: `DAILY`, `WEEKLY`, `BIWEEKLY`, `MONTHLY`.
`result.data.data.alerts[].totalDealCount`	`integer`	Yes	—	Total number of deals for this alert
`result.data.data.alerts[].deals`	`array`	Yes	—	Array of deals that matched the alert criteria (flattened from all time periods, sorted by date DESC)
`result.data.data.alerts[].deals[].id`	`string`	Yes	—	Unique identifier for the deal Format: `uuid`.
`result.data.data.alerts[].deals[].company_id`	`string`	Yes	—	Unique identifier for the company
`result.data.data.alerts[].deals[].company_name`	`string \| null`	Yes	—	Company name
`result.data.data.alerts[].deals[].company_guru_permalink`	`string \| null`	Yes	—	Fundable permalink for the company
`result.data.data.alerts[].deals[].round_type`	`string \| null`	Yes	—	Type of funding round
`result.data.data.alerts[].deals[].date`	`string \| null`	Yes	—	Date of the funding round (ISO 8601 format) Format: `date-time`.
`result.data.data.alerts[].deals[].total_round_raised`	`number \| null`	Yes	—	Total amount raised in the round (USD $M)
`result.data.data.alerts[].deals[].company_website`	`string \| null`	Yes	—	Company website domain
`result.data.data.alerts[].deals[].company_linkedin`	`string \| null`	Yes	—	Company LinkedIn URL
`result.data.data.alerts[].deals[].location`	`object`	Yes	—	Company location details
`result.data.data.alerts[].deals[].location.city`	`string \| null`	No	—	City name
`result.data.data.alerts[].deals[].location.state`	`string \| null`	No	—	State/province name
`result.data.data.alerts[].deals[].location.country`	`string \| null`	No	—	Country name
`result.data.data.alerts[].deals[].location.region`	`string \| null`	No	—	Geographic region name
`result.data.data.alerts[].deals[].deal_short_description`	`string \| null`	Yes	—	Brief description of the deal
`result.data.data.alerts[].deals[].deal_long_description`	`string \| null`	Yes	—	Detailed description of the deal
`result.data.data.alerts[].deals[].reasoning`	`string \| null`	Yes	—	AI-generated reasoning for why this deal matched the alert criteria
`result.data.data.alerts[].deals[].articles`	`array`	Yes	—	News articles related to this deal
`result.data.data.alerts[].deals[].articles[].link`	`string`	No	—	URL to the article
`result.data.data.alerts[].deals[].articles[].is_primary`	`boolean`	No	—	Whether this is the primary article for the deal
`result.data.data.alerts[].deals[].articles[].publishedDate`	`string \| null`	No	—	Article publication date (ISO 8601 format) Format: `date-time`.
`result.data.meta`	`object`	Yes	—	—
`result.data.meta.page`	`integer`	No	—	Current page number (always 0 for alerts endpoint)
`result.data.meta.page_size`	`integer`	No	—	Number of alerts queried in this request
`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