diff --git a/apps/docs/app/favicon.ico b/apps/docs/app/favicon.ico index 9aa82bcf046..b88d2804414 100644 Binary files a/apps/docs/app/favicon.ico and b/apps/docs/app/favicon.ico differ diff --git a/apps/docs/components/ui/block-info-card.tsx b/apps/docs/components/ui/block-info-card.tsx index f5085c6da17..39f3c25fbd2 100644 --- a/apps/docs/components/ui/block-info-card.tsx +++ b/apps/docs/components/ui/block-info-card.tsx @@ -9,12 +9,40 @@ interface BlockInfoCardProps { icon?: React.ComponentType<{ className?: string }> } +/** + * Brightness above which a tile background is "clearly light" and a white + * foreground icon would wash out. Mirrors apps/sim's LIGHT_TILE_THRESHOLD + * (blocks/icon-color.ts) so monochrome `currentColor` icons (e.g. Daytona, + * Notion) stay legible on white/pale tiles instead of white-on-white. + */ +const LIGHT_TILE_THRESHOLD = 0.75 + +function isLightTileColor(color: string): boolean { + const hex = color.trim().replace('#', '').toLowerCase() + let r: number + let g: number + let b: number + if (/^[0-9a-f]{3}$/.test(hex)) { + r = Number.parseInt(hex[0] + hex[0], 16) + g = Number.parseInt(hex[1] + hex[1], 16) + b = Number.parseInt(hex[2] + hex[2], 16) + } else if (/^[0-9a-f]{6}$/.test(hex)) { + r = Number.parseInt(hex.slice(0, 2), 16) + g = Number.parseInt(hex.slice(2, 4), 16) + b = Number.parseInt(hex.slice(4, 6), 16) + } else { + return false + } + return (0.299 * r + 0.587 * g + 0.114 * b) / 255 > LIGHT_TILE_THRESHOLD +} + export function BlockInfoCard({ type, color, icon: IconComponent, }: BlockInfoCardProps): React.ReactNode { const ResolvedIcon = IconComponent || blockTypeToIconMap[type] || null + const iconColorClass = isLightTileColor(color) ? 'text-black' : 'text-white' return (
{ResolvedIcon ? ( - + ) : ( -
{type.substring(0, 2)}
+
+ {type.substring(0, 2)} +
)}
) diff --git a/apps/docs/content/docs/en/integrations/brandfetch.mdx b/apps/docs/content/docs/en/integrations/brandfetch.mdx index bd4d7ee6501..ef9e2b45a63 100644 --- a/apps/docs/content/docs/en/integrations/brandfetch.mdx +++ b/apps/docs/content/docs/en/integrations/brandfetch.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#000000" /> +{/* MANUAL-CONTENT-START:intro */} +[Brandfetch](https://brandfetch.com/) is a brand data API that provides logos, colors, fonts, and firmographic information for companies, looked up by domain, stock ticker, ISIN, or crypto symbol. + +With Brandfetch, you can: + +- **Retrieve brand assets**: Pull logos, icons, and symbols in multiple formats and themes for a given brand +- **Get brand style data**: Access brand colors and fonts, including type, theme, and origin +- **Look up company info**: Retrieve firmographic data such as employees, location, and industries, along with a data quality score +- **Search for brands**: Find brands by name and get back their domains and icons + +In Sim, the Brandfetch integration allows your agents to look up a brand's logos, colors, fonts, links, and company data by domain, ticker, ISIN, or crypto symbol, or search for a brand by name to find its domain and icon. This lets agents automate tasks like enriching company records with brand assets, verifying brand identity details, or sourcing logos and color palettes for design and reporting workflows. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Brandfetch into your workflow. Retrieve brand logos, colors, fonts, and company data by domain, ticker, or name search. diff --git a/apps/docs/content/docs/en/integrations/brightdata.mdx b/apps/docs/content/docs/en/integrations/brightdata.mdx index 2cbf754f4eb..bbdac221c94 100644 --- a/apps/docs/content/docs/en/integrations/brightdata.mdx +++ b/apps/docs/content/docs/en/integrations/brightdata.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Bright Data](https://brightdata.com/) is a web data platform that provides tools for scraping, searching, and extracting structured data from websites at scale, bypassing anti-bot protections, CAPTCHAs, and IP blocks along the way. + +With Bright Data, you can: + +- **Scrape any URL**: Fetch page content through Web Unlocker, with automatic anti-bot bypassing and optional Markdown conversion +- **Search the web**: Query Google, Bing, DuckDuckGo, or Yandex through the SERP API and get structured results +- **Discover content by intent**: Run AI-powered searches that rank results by relevance to a stated goal, with optional cleaned page content for RAG +- **Run pre-built scrapers**: Trigger one of 660+ dataset scrapers for platforms like Amazon, LinkedIn, and Instagram, either synchronously for quick jobs or asynchronously via snapshots for larger ones + +In Sim, the Bright Data integration allows your agents to scrape web pages, run search-engine queries, discover and rank content by intent, and trigger structured data extraction jobs against sites like Amazon and LinkedIn. Agents can check the status of async scraping jobs, download completed snapshot results, and cancel jobs still in progress—making it possible to build workflows that gather, monitor, and retrieve web data end to end. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Bright Data into the workflow. Scrape any URL with Web Unlocker, search Google and other engines with SERP API, discover web content ranked by intent, or trigger pre-built scrapers for structured data extraction. diff --git a/apps/docs/content/docs/en/integrations/codepipeline.mdx b/apps/docs/content/docs/en/integrations/codepipeline.mdx index 155de0cb7d6..0fe8d3350e7 100644 --- a/apps/docs/content/docs/en/integrations/codepipeline.mdx +++ b/apps/docs/content/docs/en/integrations/codepipeline.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="linear-gradient(45deg, #2E27AD 0%, #527FFF 100%)" /> +{/* MANUAL-CONTENT-START:intro */} +[AWS CodePipeline](https://aws.amazon.com/codepipeline/) is a continuous delivery service that automates the build, test, and deploy phases of software release pipelines. It orchestrates pipeline stages and actions, tracking execution status, source revisions, and approval steps across a release process. + +With this integration, you can: + +- **Inspect pipelines**: List pipelines, retrieve a pipeline's stage and action structure, and check its current execution state +- **Track executions**: Get details on a specific execution or list recent executions and action-level history, including status, triggers, and source revisions +- **Control pipeline flow**: Start or stop executions, retry failed stages, and approve or reject pending manual approval actions +- **Manage stage transitions**: Disable or re-enable artifact transitions into or out of a stage to freeze or resume a pipeline + +In Sim, the AWS CodePipeline integration allows your agents to monitor and control release pipelines programmatically — listing pipelines and their structure, checking execution and action status, starting or stopping executions, retrying failed stages, approving or rejecting manual approvals, and enabling or disabling stage transitions. This lets your agents build deployment automation and approval workflows that respond to pipeline state in real time. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate AWS CodePipeline into workflows. Start, stop, and monitor pipeline executions, retry failed stages, and approve or reject manual approval actions. Requires AWS access key and secret access key. diff --git a/apps/docs/content/docs/en/integrations/context_dev.mdx b/apps/docs/content/docs/en/integrations/context_dev.mdx index 3cd1687a0fc..6f70c82773a 100644 --- a/apps/docs/content/docs/en/integrations/context_dev.mdx +++ b/apps/docs/content/docs/en/integrations/context_dev.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#ffffff" /> +{/* MANUAL-CONTENT-START:intro */} +[Context.dev](https://context.dev/) is a web data API that scrapes, crawls, searches, and extracts data from the web, and resolves brand and company data from a domain, name, email, ticker, or transaction descriptor. + +With Context.dev, you can: + +- **Scrape and crawl pages**: Convert URLs to clean markdown or HTML, capture screenshots, discover images, crawl entire sites, and map sitemaps +- **Search the web**: Run natural language searches with domain filters and optional markdown scraping of results +- **Extract structured data**: Pull data matching a JSON schema, or detect and extract product details and catalogs from a page or domain +- **Analyze brand and design data**: Extract a domain's fonts and design system, classify a brand into NAICS/SIC industry codes, and resolve brand data (logos, colors, socials, address) from a domain, company name, email, ticker, or transaction descriptor + +In Sim, the Context.dev integration allows your agents to scrape and crawl web pages into markdown or HTML, capture screenshots, search the web, extract structured data and product information, pull a site's fonts and style guide, classify a brand's industry, and look up brand assets and company details by domain, name, email, ticker, or transaction — all through a single set of API calls in your workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Context.dev into the workflow. Scrape pages to markdown or HTML, capture screenshots, list images, crawl entire sites, map sitemaps, search the web, extract structured data and products, pull design systems, classify industries, and retrieve brand assets by domain, name, email, ticker, or transaction — all from one API. @@ -570,31 +584,6 @@ Retrieve brand data for a public company by its stock ticker symbol. | ↳ `links` | json | Key brand links \(careers, privacy, terms, blog, pricing, contact\) | | ↳ `primary_language` | string | Primary language of the brand site | -### `context_dev_get_brand_simplified` - -Retrieve essential brand data for a domain: title, colors, logos, and backdrops. - -#### Input - -| Parameter | Type | Required | Description | -| --------- | ---- | -------- | ----------- | -| `domain` | string | Yes | The domain to retrieve simplified brand data for \(e.g., "airbnb.com"\) | -| `maxAgeMs` | number | No | Cache max age in milliseconds \(86400000-31536000000, default: 7776000000\) | -| `timeoutMS` | number | No | Request timeout in milliseconds \(1000-300000\) | -| `apiKey` | string | Yes | Context.dev API key | - -#### Output - -| Parameter | Type | Description | -| --------- | ---- | ----------- | -| `status` | string | Retrieval status | -| `brand` | object | Simplified brand data \(domain, title, colors, logos, backdrops\) | -| ↳ `domain` | string | Brand domain | -| ↳ `title` | string | Brand title | -| ↳ `colors` | json | Brand colors \(hex and name\) | -| ↳ `logos` | json | Brand logos with mode, colors, resolution, and type | -| ↳ `backdrops` | json | Brand backdrop images | - ### `context_dev_identify_transaction` Identify the brand behind a raw bank/card transaction descriptor and return its brand data. @@ -637,44 +626,4 @@ Identify the brand behind a raw bank/card transaction descriptor and return its | ↳ `links` | json | Key brand links \(careers, privacy, terms, blog, pricing, contact\) | | ↳ `primary_language` | string | Primary language of the brand site | -### `context_dev_prefetch_domain` - -Queue a domain for brand-data prefetching to reduce latency on later requests (subscribers; 0 credits). - -#### Input - -| Parameter | Type | Required | Description | -| --------- | ---- | -------- | ----------- | -| `domain` | string | Yes | The domain to prefetch brand data for \(e.g., "example.com"\) | -| `timeoutMS` | number | No | Request timeout in milliseconds \(1000-300000\) | -| `apiKey` | string | Yes | Context.dev API key | - -#### Output - -| Parameter | Type | Description | -| --------- | ---- | ----------- | -| `status` | string | Prefetch status | -| `message` | string | Human-readable prefetch result message | -| `domain` | string | The domain queued for prefetching | - -### `context_dev_prefetch_by_email` - -Queue an email's domain for brand-data prefetching to reduce later latency (subscribers; 0 credits). Free/disposable emails are rejected. - -#### Input - -| Parameter | Type | Required | Description | -| --------- | ---- | -------- | ----------- | -| `email` | string | Yes | Work email address whose domain should be prefetched \(free providers rejected\) | -| `timeoutMS` | number | No | Request timeout in milliseconds \(1000-300000\) | -| `apiKey` | string | Yes | Context.dev API key | - -#### Output - -| Parameter | Type | Description | -| --------- | ---- | ----------- | -| `status` | string | Prefetch status | -| `message` | string | Human-readable prefetch result message | -| `domain` | string | The domain queued for prefetching | - diff --git a/apps/docs/content/docs/en/integrations/crowdstrike.mdx b/apps/docs/content/docs/en/integrations/crowdstrike.mdx index 92abd6aa84d..97b1e939963 100644 --- a/apps/docs/content/docs/en/integrations/crowdstrike.mdx +++ b/apps/docs/content/docs/en/integrations/crowdstrike.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#E01F3D" /> +{/* MANUAL-CONTENT-START:intro */} +[CrowdStrike](https://www.crowdstrike.com/) is a cybersecurity platform providing endpoint protection, threat intelligence, and identity security through its Falcon suite. This integration connects to the Falcon Identity Protection API to query sensor data. + +With this integration, you can: + +- **Search sensors**: Query CrowdStrike identity protection sensors by hostname, IP, or related fields using Falcon Query Language filters +- **Fetch sensor details**: Retrieve documented sensor details, including protection status, policy assignments, and protocol configuration, for one or more device IDs +- **Run sensor aggregates**: Execute documented JSON aggregate queries to summarize sensor data into buckets and metrics + +In Sim, the CrowdStrike integration allows your agents to search identity protection sensors, look up detailed sensor records by device ID, and run aggregate queries against sensor data—all authenticated with a Falcon API client ID and secret against a specified cloud region. This lets agents surface device protection status, policy coverage, and protocol configuration (Kerberos, LDAP, NTLM, RDP, SMB) as part of security monitoring and reporting workflows. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate CrowdStrike Identity Protection into workflows to search sensors, fetch documented sensor details by device ID, and run documented sensor aggregate queries. diff --git a/apps/docs/content/docs/en/integrations/deployments.mdx b/apps/docs/content/docs/en/integrations/deployments.mdx index 17251cc0269..6b13fd2e622 100644 --- a/apps/docs/content/docs/en/integrations/deployments.mdx +++ b/apps/docs/content/docs/en/integrations/deployments.mdx @@ -10,6 +10,17 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#0C0C0C" /> +{/* MANUAL-CONTENT-START:intro */} +Deployments is Sim's built-in system for taking a workflow's draft state live for API execution and managing its version history. Every deploy creates a new version, and past versions stay available for review or rollback. + +- **Deploy and undeploy**: Push the current draft live as a new version, or take a live workflow offline and remove its triggers, webhooks, and schedules +- **Promote or roll back**: Make any past version the live one without creating a new version, including re-deploying an undeployed workflow at a known-good version +- **Inspect version history**: List every deployment version with its metadata, or fetch the full workflow state snapshot for a specific version + +In Sim, the Deployments block allows your agents to deploy and undeploy workflows, promote a specific version to live for rollbacks, list all deployment versions of a workflow, and retrieve the deployed state snapshot of any past version—all programmatically as part of another workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Deploy, undeploy, and roll back workflows in the current workspace. Promote a previous deployment version to live, list every version, or fetch the deployed workflow state for a specific version. diff --git a/apps/docs/content/docs/en/integrations/downdetector.mdx b/apps/docs/content/docs/en/integrations/downdetector.mdx index 25bf65df90a..6aa3768cd64 100644 --- a/apps/docs/content/docs/en/integrations/downdetector.mdx +++ b/apps/docs/content/docs/en/integrations/downdetector.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Downdetector](https://downdetector.com/) is an outage-tracking service that aggregates user-submitted reports to detect and visualize real-time service disruptions for thousands of companies. The Downdetector Enterprise API exposes this data programmatically for monitoring and alerting. + +With Downdetector, you can: + +- **Search and identify companies**: Look up monitored companies by name, slug, country, or category to get their ids and status page URLs +- **Check current status and trends**: Read a company's cached status, 24h report statistics, and baseline to judge whether current activity is abnormal +- **Inspect problem indicators**: See which specific issues (e.g. "Login", "App crashing") are being reported and in what proportion +- **Track incidents and events**: Pull incident timelines, published events, and attribution data (internal vs. external cause, user impact) for outages + +In Sim, the Downdetector integration allows your agents to search for monitored companies, check their current status and baseline reports, retrieve near-real-time report counts and problem indicators, and pull incident, event, and attribution data — all programmatically through API calls. This enables your agents to power outage alerts, monitoring dashboards, and automated incident summaries that stay current with service disruptions across the companies and regions Downdetector tracks. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Track real-time service outages with the Downdetector Enterprise API. Search monitored companies, read their current status and report trends, inspect problem indicators, and pull incident timelines to power outage alerts and dashboards. Requires a Downdetector Enterprise API plan. diff --git a/apps/docs/content/docs/en/integrations/emailbison.mdx b/apps/docs/content/docs/en/integrations/emailbison.mdx index 8a3050d5d50..75b90e492f0 100644 --- a/apps/docs/content/docs/en/integrations/emailbison.mdx +++ b/apps/docs/content/docs/en/integrations/emailbison.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FB7A22" /> +{/* MANUAL-CONTENT-START:intro */} +[Email Bison](https://emailbison.com/) is a cold email outreach and deliverability platform for managing leads, sending sequences, and tracking campaign performance. + +With Email Bison, you can: + +- **Manage leads**: Create, update, retrieve, and tag leads, and track their engagement across campaigns +- **Run campaigns**: Create campaigns, attach leads, and pause, resume, or archive them as needed +- **Track replies**: List and filter incoming replies by status, folder, campaign, sender, lead, or tag +- **React to events**: Trigger workflows on first email sent, interested replies, unsubscribes, bounces, opens, and sender account changes + +In Sim, the Email Bison integration allows your agents to create and update leads, list and filter leads/campaigns/replies, attach leads to campaigns, manage campaign status, and organize leads with tags — all programmatically through API calls. Combined with Email Bison triggers, agents can also react in real time to events like a contact being emailed, replying, marking interest, unsubscribing, or an email bouncing, making it possible to automate outbound outreach workflows end to end. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Email Bison into workflows. Create and update leads, manage campaigns, attach leads to campaigns, list replies, and organize leads with tags. diff --git a/apps/docs/content/docs/en/integrations/enrichment.mdx b/apps/docs/content/docs/en/integrations/enrichment.mdx index 702ceb50cf8..664eac18132 100644 --- a/apps/docs/content/docs/en/integrations/enrichment.mdx +++ b/apps/docs/content/docs/en/integrations/enrichment.mdx @@ -10,6 +10,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#9333EA" /> +{/* MANUAL-CONTENT-START:intro */} +Data Enrichment is a built-in Sim block that looks up missing data — work email, phone number, company domain, company info, and more — from fields you map in from your workflow. It runs a registered enrichment (like "Work Email" or "Phone Number") against the same provider cascade used by table enrichments, trying multiple providers until one returns a match. + +In Sim, the enrichment block allows your agents to fill in gaps in a record by supplying an enrichment id and a map of input values, then reading back whether a match was found and which provider (e.g. Hunter, People Data Labs) supplied the result. This lets workflows enrich leads or contacts inline — for example, taking a name and company and resolving a work email — without agents needing to call each provider's API directly. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Run a Sim enrichment to look up data — work email, phone number, company domain, company info, and more — from the fields you map in. Uses the same provider cascade as table enrichments. diff --git a/apps/docs/content/docs/en/integrations/extend.mdx b/apps/docs/content/docs/en/integrations/extend.mdx index d0a31696b13..234a361a039 100644 --- a/apps/docs/content/docs/en/integrations/extend.mdx +++ b/apps/docs/content/docs/en/integrations/extend.mdx @@ -10,6 +10,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#000000" /> +{/* MANUAL-CONTENT-START:intro */} +[Extend](https://www.extend.ai/) is a document processing platform that uses AI to parse and extract structured content from documents, turning unstructured files into usable data. + +In Sim, the Extend integration allows your agents to submit a document for parsing and receive back the processed content as structured chunks and block-level elements, along with the page count and credits consumed by the run. This enables workflows to pull structured data out of documents—such as PDFs or other file references—for downstream steps to consume, without manually building document-parsing logic. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Extend AI into the workflow. Parse and extract structured content from documents or file references. diff --git a/apps/docs/content/docs/en/integrations/file.mdx b/apps/docs/content/docs/en/integrations/file.mdx index f4c7da583c9..f0710cb9bf3 100644 --- a/apps/docs/content/docs/en/integrations/file.mdx +++ b/apps/docs/content/docs/en/integrations/file.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#F5F5F5" /> +{/* MANUAL-CONTENT-START:intro */} +The File block is a built-in Sim block for working with files stored in the workspace, or fetched from external URLs. It handles reading, writing, appending, compressing, decompressing, and sharing files as part of a workflow. + +With the File block, you can: + +- **Read and extract content**: Load workspace file objects and extract their text content +- **Fetch from URLs**: Retrieve and parse files from external URLs with custom headers +- **Write and append**: Create new workspace files or append content to existing ones +- **Compress and decompress**: Bundle files into a .zip archive or extract an archive into the workspace +- **Manage sharing**: Enable or disable a public share link for a file, with public, password, email, or SSO access modes + +In Sim, the File block allows your agents to read and extract text from workspace files, fetch and parse files from URLs, write or append content to files, bundle files into or out of .zip archives, and control public sharing access for a file—all programmatically as steps in a workflow. This makes it possible to move file content into and out of a workflow, package outputs for download or transfer, and expose files to external users through a managed share link. +{/* MANUAL-CONTENT-END */} + ## Usage Instructions Read workspace file objects, extract the text content of files, fetch and parse files from URLs with optional headers, write new workspace files, append content to existing files, compress files into a .zip archive, extract a .zip archive into the workspace, or manage the public share link for a file. diff --git a/apps/docs/content/docs/en/integrations/google_contacts.mdx b/apps/docs/content/docs/en/integrations/google_contacts.mdx index 3a98b2aea67..242143a7f7b 100644 --- a/apps/docs/content/docs/en/integrations/google_contacts.mdx +++ b/apps/docs/content/docs/en/integrations/google_contacts.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Google Contacts](https://contacts.google.com/) is Google's contact management service, letting people store and organize names, emails, phone numbers, and organization details for everyone they communicate with. + +With this block, you can: + +- **Create and update contacts**: Add new contacts or edit existing ones with names, emails, phone numbers, organization, job title, and notes +- **Retrieve and list contacts**: Fetch a specific contact by resource name or list contacts with pagination and sort order +- **Search and delete contacts**: Find contacts by name, email, phone, or organization, or remove a contact entirely + +In Sim, the Google Contacts integration allows your agents to create, read, update, delete, list, and search contacts programmatically within a workflow. This enables agents to keep a contact directory in sync, look up contact details before sending communications, or search for matching contacts by name, email, phone, or organization as part of a larger automation. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Google Contacts into the workflow. Can create, read, update, delete, list, and search contacts. diff --git a/apps/docs/content/docs/en/integrations/granola.mdx b/apps/docs/content/docs/en/integrations/granola.mdx index e1d96ad531d..9f5371c782b 100644 --- a/apps/docs/content/docs/en/integrations/granola.mdx +++ b/apps/docs/content/docs/en/integrations/granola.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#B2C147" /> +{/* MANUAL-CONTENT-START:intro */} +[Granola](https://www.granola.ai/) is an AI notepad for meetings that automatically records and transcribes calls, then generates structured notes and summaries alongside your own typed notes. + +With Granola, you can: + +- **List meeting notes**: Browse notes with date filters, folder scoping, and pagination +- **Retrieve full note details**: Get summaries, attendees, calendar event details, and transcripts for a specific note +- **Organize by folders**: List and filter notes using Granola's folder structure + +In Sim, the Granola integration allows your agents to pull meeting notes, summaries, and transcripts directly into a workflow. Agents can list recent notes with date or folder filters, fetch a specific note's summary text, attendees, and calendar details, retrieve the full transcript with speaker labels when needed, and browse folders to organize retrieval. This makes it possible to build workflows that surface meeting outcomes, route action items, or feed meeting context into downstream agent reasoning. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Granola into your workflow to retrieve meeting notes, summaries, attendees, and transcripts. diff --git a/apps/docs/content/docs/en/integrations/instantly.mdx b/apps/docs/content/docs/en/integrations/instantly.mdx index 2dd0ae4923f..538ae932aec 100644 --- a/apps/docs/content/docs/en/integrations/instantly.mdx +++ b/apps/docs/content/docs/en/integrations/instantly.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Instantly](https://instantly.ai/) is a cold email outreach platform used to send, manage, and scale email campaigns to leads. It provides tools for lead management, campaign scheduling, and reply tracking through its Unibox inbox. + +With Instantly, you can: + +- **Manage leads**: Create, update, search, and delete leads across campaigns and lead lists +- **Run campaigns**: Create, update, activate, pause, and delete email campaigns with custom schedules and sequences +- **Handle replies**: List Unibox emails and reply to leads directly from a connected sending account +- **Organize lead lists**: Create and list lead lists, and track lead interest status + +In Sim, the Instantly integration allows your agents to manage leads and campaigns programmatically — retrieving and creating leads, updating lead interest status, listing and controlling campaigns (create, patch, activate, pause, delete), reading and replying to Unibox emails, and creating or listing lead lists. This lets your agents automate outbound email workflows, such as syncing new leads into campaigns, monitoring campaign status, and responding to replies without leaving the workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Instantly API V2 into workflows. Create, update, and list leads, manage lead interest status, delete leads in bulk, list, create, patch, activate, pause, and delete campaigns, reply to emails, and manage lead lists. diff --git a/apps/docs/content/docs/en/integrations/jupyter.mdx b/apps/docs/content/docs/en/integrations/jupyter.mdx index 81c333a73f2..e62f270a9e6 100644 --- a/apps/docs/content/docs/en/integrations/jupyter.mdx +++ b/apps/docs/content/docs/en/integrations/jupyter.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Jupyter](https://jupyter.org/) is an open-source platform for interactive computing, best known for the Jupyter Notebook interface that combines live code, visualizations, and narrative text. It runs as a server that exposes files, notebooks, kernels, and sessions over an HTTP API. + +With Jupyter, you can: + +- **Manage files and notebooks**: List, read, create, upload, rename, copy, and delete files, notebooks, and directories +- **Control kernels**: List, start, stop, restart, and interrupt the runtimes that execute notebook code +- **Manage sessions**: List, create, and delete sessions that bind a notebook path to a running kernel + +In Sim, the Jupyter integration allows your agents to connect to a self-hosted Jupyter server and drive it programmatically—browsing and editing files and notebooks, uploading content, and managing kernels and sessions that bind notebooks to running code environments. This lets your agents automate notebook-based workflows, such as provisioning a kernel, writing or updating notebook content, and cleaning up sessions and files as part of a larger pipeline. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate a self-hosted Jupyter server into the workflow. Browse, read, create, upload, rename, copy, and delete files and notebooks; start, stop, restart, and interrupt kernels; and manage sessions that bind notebooks to kernels. diff --git a/apps/docs/content/docs/en/integrations/logs.mdx b/apps/docs/content/docs/en/integrations/logs.mdx index 2295215662c..6237f56c9c1 100644 --- a/apps/docs/content/docs/en/integrations/logs.mdx +++ b/apps/docs/content/docs/en/integrations/logs.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#EAB308" /> +{/* MANUAL-CONTENT-START:intro */} +The Logs block gives agents programmatic access to workflow run history in the current workspace. It queries the same run data shown on the Logs page and can fetch full execution detail for any individual run. + +With Logs, you can: + +- **Query run history**: Filter runs by workflow, folder, status, trigger type, date range, cost, and duration, with sorting and free-text search +- **Fetch run details**: Retrieve a specific run's status, trigger, timing, cost, and final output by run ID +- **Inspect execution traces**: Pull the full trace spans for a run to see how it executed step by step + +In Sim, the Logs block allows your agents to search and filter workflow run history using the same filters available on the Logs page, then drill into a specific run to retrieve its status, cost, duration, final output, and full trace spans. This lets agents monitor other workflows, audit past executions, and pull execution details programmatically as part of a larger workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Query workflow run logs in the current workspace with the same filters as the Logs page, returning matching run IDs. Fetch full details for a single run, including its trace spans. diff --git a/apps/docs/content/docs/en/integrations/monday.mdx b/apps/docs/content/docs/en/integrations/monday.mdx index 35a2e25eced..4e4941f2c9e 100644 --- a/apps/docs/content/docs/en/integrations/monday.mdx +++ b/apps/docs/content/docs/en/integrations/monday.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Monday.com](https://monday.com/) is a work operating system that teams use to plan, track, and manage projects through customizable boards, items, and columns. Boards organize work into groups of items, with columns tracking status, dates, people, and other structured data for each item. + +With Monday.com, you can: + +- **Manage boards**: List, retrieve, and create boards along with their groups and columns +- **Manage items**: Fetch, search, create, update, duplicate, archive, and delete items +- **Organize work**: Create subitems, move items between groups, and add updates or comments +- **React to events**: Trigger workflows on column changes, item creation, status changes, and more + +In Sim, the Monday.com integration allows your agents to list and inspect boards, fetch and search items by column values, create and update items and subitems, change column values, move items between groups, post updates, and create new boards, groups, and columns—all programmatically through API calls. Triggers let workflows react automatically to events such as column value changes, item creation or deletion, status changes, items being moved between groups, and updates being posted, making it possible to keep external systems in sync with activity on a Monday.com board. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate with Monday.com to list boards, get board details, fetch and search items, create and update items, archive or delete items, create subitems, move items between groups, add updates, and create groups. diff --git a/apps/docs/content/docs/en/integrations/mysql.mdx b/apps/docs/content/docs/en/integrations/mysql.mdx index 35202422f41..b9ffd5979c5 100644 --- a/apps/docs/content/docs/en/integrations/mysql.mdx +++ b/apps/docs/content/docs/en/integrations/mysql.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[MySQL](https://www.mysql.com/) is a widely used open-source relational database system. The MySQL block connects your workflow directly to a MySQL database, letting you read and write data without leaving Sim. It handles the connection details—host, port, database, credentials, and SSL mode—so blocks can query, insert, update, delete, and execute raw SQL against your database. + +With the MySQL block, you can: + +- **Query data**: Run SELECT statements and get back rows with a row count +- **Insert, update, and delete records**: Write key-value data to a table or modify existing rows with a WHERE clause +- **Execute raw SQL**: Run arbitrary SQL statements, such as DDL for creating tables +- **Introspect the schema**: Retrieve table structures, columns, keys, indexes, and the list of available databases on the server + +In Sim, the MySQL block allows your agents to read from and write to a MySQL database as part of a workflow—querying records to feed downstream logic, inserting or updating rows based on agent output, cleaning up data with deletes, running custom SQL for one-off operations, and introspecting the schema to understand table structure before generating queries. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate MySQL into the workflow. Can query, insert, update, delete, and execute raw SQL. diff --git a/apps/docs/content/docs/en/integrations/postgresql.mdx b/apps/docs/content/docs/en/integrations/postgresql.mdx index a864f4b4b4f..ac0e70b4382 100644 --- a/apps/docs/content/docs/en/integrations/postgresql.mdx +++ b/apps/docs/content/docs/en/integrations/postgresql.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#336791" /> +{/* MANUAL-CONTENT-START:intro */} +[PostgreSQL](https://www.postgresql.org/) is a widely used open-source relational database system known for reliability, extensibility, and standards compliance. It stores structured data in tables and supports SQL for querying, transactions, and schema management. + +With this integration, you can: + +- **Query data**: Run SELECT statements to retrieve rows from a database +- **Insert, update, and delete data**: Write, modify, and remove rows in a table +- **Execute raw SQL**: Run arbitrary SQL statements directly against the database +- **Introspect schemas**: Retrieve table structures, columns, primary/foreign keys, and indexes + +In Sim, the PostgreSQL integration allows your agents to connect to a PostgreSQL database and query, insert, update, delete, and execute raw SQL against it, as well as introspect the database schema to discover tables, columns, and relationships. This gives your agents the ability to read and write structured data as part of a workflow, and to understand a database's structure before generating or running queries against it. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate PostgreSQL into the workflow. Can query, insert, update, delete, and execute raw SQL. diff --git a/apps/docs/content/docs/en/integrations/rb2b.mdx b/apps/docs/content/docs/en/integrations/rb2b.mdx index 45096416cfc..35d5234e709 100644 --- a/apps/docs/content/docs/en/integrations/rb2b.mdx +++ b/apps/docs/content/docs/en/integrations/rb2b.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#51FF00" /> +{/* MANUAL-CONTENT-START:intro */} +[RB2B](https://rb2b.com/) is a website visitor identification and B2B enrichment platform that resolves anonymous website traffic into person-level identity data. It matches IP addresses, hashed emails, and LinkedIn profiles against its data graph to surface who is visiting a site and how to reach them. + +With RB2B, you can: + +- **Resolve IPs into identity signals**: Convert an IP address into hashed emails, mobile advertising IDs, or company domains +- **Enrich emails and LinkedIn profiles**: Turn a hashed email or LinkedIn slug into a full business profile with name, title, company, and contact details +- **Look up contact and activity data**: Retrieve mobile phone numbers, personal emails, and last-active dates for a known contact +- **Search for people**: Find a LinkedIn profile from a first name, last name, and company domain + +In Sim, the RB2B integration allows your agents to identify anonymous website visitors and enrich them into actionable contact records — resolving an IP address to a company or hashed email, expanding a hashed email or LinkedIn profile into a full business profile, and retrieving mobile phone numbers or personal emails for outreach. Agents can also check remaining API credits and confirm when a contact was last active, making the integration useful for lead identification, sales prospecting, and B2B enrichment workflows. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Resolve IP addresses, hashed emails, and LinkedIn profiles into person-level identity and B2B enrichment data using the RB2B API. Convert IPs to hashed emails, MAIDs, and company domains; enrich emails into LinkedIn profiles, business profiles, and mobile IDs; and look up emails or phone numbers from LinkedIn. Requires an RB2B API key. diff --git a/apps/docs/content/docs/en/integrations/sftp.mdx b/apps/docs/content/docs/en/integrations/sftp.mdx index 43fdffe9a9f..65a8a68fba6 100644 --- a/apps/docs/content/docs/en/integrations/sftp.mdx +++ b/apps/docs/content/docs/en/integrations/sftp.mdx @@ -10,6 +10,21 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#2D3748" /> +{/* MANUAL-CONTENT-START:intro */} +SFTP (SSH File Transfer Protocol) is a secure file transfer protocol that runs over an SSH connection, letting you move and manage files on a remote server without exposing credentials or data in plaintext. It supports authentication via password or private key, making it a standard choice for secure file exchange with servers, hosting providers, and legacy systems. + +With this block, you can: + +- **Upload files**: Send files or direct text content to a directory on a remote server +- **Download files**: Retrieve a file from the remote server as text or base64-encoded content +- **List directory contents**: Browse files and folders, optionally with detailed metadata like size and permissions +- **Delete files or directories**: Remove remote files, with optional recursive deletion for directories +- **Create directories**: Make new directories on the remote server, optionally creating parent directories as needed + +In Sim, the SFTP block allows your agents to upload, download, list, delete, and create files and directories on a remote server, all authenticated with a password or private key. This enables workflows that move generated files to a remote destination, pull files from a server for processing, sync directory contents, or manage remote file structures as part of a larger automation. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Upload, download, list, and manage files on remote servers via SFTP. Supports both password and private key authentication for secure file transfers. diff --git a/apps/docs/content/docs/en/integrations/sixtyfour.mdx b/apps/docs/content/docs/en/integrations/sixtyfour.mdx index cec9052552a..6a10ddd42c1 100644 --- a/apps/docs/content/docs/en/integrations/sixtyfour.mdx +++ b/apps/docs/content/docs/en/integrations/sixtyfour.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#000000" /> +{/* MANUAL-CONTENT-START:intro */} +[Sixtyfour AI](https://sixtyfour.ai/) is an AI-powered research platform that finds contact information and enriches lead and company data by researching the web. It combines automated search with structured data extraction to surface emails, phone numbers, and detailed profile information. + +With Sixtyfour AI, you can: + +- **Find phone numbers**: Locate phone numbers for a lead using their name, company, LinkedIn URL, or other identifying details +- **Find email addresses**: Discover professional or personal email addresses, complete with validation status +- **Enrich leads**: Research a person and return structured data matching custom fields, backed by source references and a confidence score +- **Enrich companies**: Research a company, optionally finding associated people and a full org chart, with results matching custom fields + +In Sim, the Sixtyfour AI integration allows your agents to look up phone numbers and emails for a lead, and enrich lead or company records with structured research data, source references, and confidence scores—all programmatically through API calls. This enables your agents to turn partial contact information into complete, verified profiles, and to build out organizational data such as employee counts and org charts as part of a workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Find emails, phone numbers, and enrich lead or company data with contact information, social profiles, and detailed research using Sixtyfour AI. diff --git a/apps/docs/content/docs/en/integrations/smtp.mdx b/apps/docs/content/docs/en/integrations/smtp.mdx index 0e4bec244ac..1e65fc3c0ce 100644 --- a/apps/docs/content/docs/en/integrations/smtp.mdx +++ b/apps/docs/content/docs/en/integrations/smtp.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#2D3748" /> +{/* MANUAL-CONTENT-START:intro */} +The SMTP block sends email through any standard SMTP mail server, including Gmail, Outlook, and self-hosted or custom mail servers. It connects directly using the server hostname, port, and credentials you provide rather than a vendor-specific API. + +With the SMTP block, you can: + +- **Connect to any SMTP server**: Configure host, port, and security protocol (TLS, SSL, or none) for the mail server of your choice +- **Control message content and formatting**: Set sender, recipients, subject, and body, with support for either plain text or HTML content +- **Reach multiple recipients and attach files**: Add CC and BCC recipients, set a reply-to address, and attach files to the outgoing email + +In Sim, the SMTP block allows your agents to send emails as part of a workflow by supplying connection details and message content, then confirming delivery through the returned success status and message ID. This makes it possible to notify recipients, deliver generated reports, or trigger email-based alerts directly from a workflow, with the block reporting the message ID on success or an error message if sending fails. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Send emails using any SMTP server (Gmail, Outlook, custom servers, etc.). Configure SMTP connection settings and send emails with full control over content, recipients, and attachments. diff --git a/apps/docs/content/docs/en/integrations/sportmonks.mdx b/apps/docs/content/docs/en/integrations/sportmonks.mdx index f3d3d673742..90285fda99e 100644 --- a/apps/docs/content/docs/en/integrations/sportmonks.mdx +++ b/apps/docs/content/docs/en/integrations/sportmonks.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#171534" /> +{/* MANUAL-CONTENT-START:intro */} +[Sportmonks](https://www.sportmonks.com/) is a sports data provider offering structured APIs for football, motorsport, odds, and reference data used to power scores, statistics, and betting-related applications. + +With Sportmonks, you can access: + +- **Football data**: fixtures, livescores, leagues, seasons, stages, rounds, teams, squads, players, coaches, referees, venues, standings, topscorers, transfers, schedules, commentaries, TV stations, rivals, expected goals (xG), and predictions +- **Motorsport data**: sessions, drivers, teams, championship standings, laps, and pitstops +- **Odds data**: pre-match and in-play odds, bookmakers, and markets +- **Core reference data**: continents, countries, regions, cities, types, and time zones + +In Sim, the Sportmonks integration allows your agents to query fixtures, player and team statistics, transfer activity, standings, and odds directly within a workflow. Agents can pull expected goals (xG) by player or team, retrieve match commentaries and brackets, look up coaches and their histories, and enrich any of these with related data through the `include` parameter—enabling workflows that build match reports, track transfer rumours, or surface live odds and predictions. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate the Sportmonks sports data APIs into the workflow from a single block. Football: fixtures, livescores, leagues, seasons, stages, rounds, teams, squads, players, coaches, referees, venues, standings, topscorers, transfers, schedules, commentaries, TV stations, rivals, expected goals (xG), and predictions. Motorsport: sessions, drivers, teams, championship standings, laps, and pitstops. Odds: pre-match and in-play odds, bookmakers, and markets. Core: continents, countries, regions, cities, types, and time zones. diff --git a/apps/docs/content/docs/en/integrations/square.mdx b/apps/docs/content/docs/en/integrations/square.mdx index d741dbdb24d..9508ce539f5 100644 --- a/apps/docs/content/docs/en/integrations/square.mdx +++ b/apps/docs/content/docs/en/integrations/square.mdx @@ -10,6 +10,20 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#000000" /> +{/* MANUAL-CONTENT-START:intro */} +[Square](https://squareup.com/) is a commerce platform that provides payment processing, point-of-sale, and business management tools for businesses of all sizes. It offers APIs for accepting payments, managing customers, and handling orders, invoices, and catalog data across online and in-person sales channels. + +With Square, you can: + +- **Process payments and refunds**: Take, retrieve, list, cancel, complete, and refund payments +- **Manage customers**: Create, retrieve, list, search, update, and delete customer profiles +- **Manage orders and invoices**: Create, retrieve, search, and pay for orders, and create, publish, cancel, and delete invoices +- **Manage catalog and inventory**: Upsert, retrieve, list, and search catalog objects, upload catalog images, and check inventory counts + +In Sim, the Square integration allows your agents to take and refund payments, manage customer profiles, look up business locations, create and track orders and invoices, and manage catalog items and inventory — all programmatically through API calls. This enables agents to handle real commerce operations such as charging a customer, issuing a refund, keeping customer records up to date, sending invoices, and maintaining product catalog and stock data, directly from a workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Square into the workflow. Take and refund payments, manage customers, build catalog items and images, create and search orders, and issue invoices. Authenticate with a Square access token (personal access token). diff --git a/apps/docs/content/docs/en/integrations/ssh.mdx b/apps/docs/content/docs/en/integrations/ssh.mdx index 74a830b9edc..3b059a04bb8 100644 --- a/apps/docs/content/docs/en/integrations/ssh.mdx +++ b/apps/docs/content/docs/en/integrations/ssh.mdx @@ -10,6 +10,19 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#000000" /> +{/* MANUAL-CONTENT-START:intro */} +The SSH block connects to remote servers using the Secure Shell protocol, supporting both password and private key (OpenSSH format) authentication. It provides direct command execution and file system access on any server reachable over SSH. + +With SSH, you can: + +- **Run commands and scripts**: Execute shell commands or upload and run multi-line scripts with a configurable interpreter +- **Manage the file system**: Upload, download, read, write, move, rename, and delete files and directories +- **Inspect the remote environment**: Check whether a command or path exists, list directory contents, and retrieve system information such as OS, architecture, uptime, and disk/memory usage + +In Sim, the SSH block allows your agents to operate remote servers as part of a workflow—running commands and scripts, transferring and manipulating files, and gathering system diagnostics—all through authenticated SSH connections. This makes it possible to automate server administration, deployment steps, and remote data processing directly from an agent's workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Execute commands, transfer files, and manage remote servers via SSH. Supports password and private key authentication for secure server access. diff --git a/apps/docs/content/docs/en/integrations/thrive.mdx b/apps/docs/content/docs/en/integrations/thrive.mdx index d2987593bad..fa2be184eb7 100644 --- a/apps/docs/content/docs/en/integrations/thrive.mdx +++ b/apps/docs/content/docs/en/integrations/thrive.mdx @@ -10,6 +10,21 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#FFFFFF" /> +{/* MANUAL-CONTENT-START:intro */} +[Thrive Learning](https://thrivelearning.com/) is a learning management and compliance platform that helps organizations manage user onboarding, training assignments, and CPD tracking. It gives HR and L&D teams a central system for organizing learners into audiences, assigning content, and monitoring completion and compliance status. + +With Thrive, you can: + +- **Manage the user lifecycle**: Create, update, suspend, and delete users, and look them up by ID or ref +- **Organize audiences and structures**: Create and manage audiences, move them between parents, and manage their members and managers +- **Assign and track compliance**: Create assignments tied to content and audiences, and list or inspect the resulting enrolments +- **Record learning outcomes**: Create and query completion records, including skills acquired and RPL imports +- **Access content and activity data**: Look up content items and query user activity records + +In Sim, the Thrive Learning integration allows your agents to manage the full user lifecycle, organize audiences and their members and managers, create and track compliance assignments and enrolments, record and query learning completions, and retrieve content and activity records — all programmatically through API calls. This enables agents to automate onboarding, training assignment, and compliance reporting workflows directly against Thrive's tenant. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Thrive Learning into the workflow. Manage user lifecycle, audiences and their members and managers, content assignments and enrolments, learning completions, content and activity records, CPD, tags, and skills. diff --git a/apps/docs/content/docs/en/integrations/twilio.mdx b/apps/docs/content/docs/en/integrations/twilio.mdx index 6de83ac0136..eb72d6f7405 100644 --- a/apps/docs/content/docs/en/integrations/twilio.mdx +++ b/apps/docs/content/docs/en/integrations/twilio.mdx @@ -10,6 +10,18 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#6B7280" /> +{/* MANUAL-CONTENT-START:intro */} +[Twilio](https://www.twilio.com/) is a cloud communications platform that lets developers programmatically send and receive SMS, MMS, and voice calls. It provides a widely used API for building messaging into applications, including delivery status callbacks and inbound message handling. + +With the Twilio triggers, you can: + +- **React to message status changes**: Start a workflow whenever a sent message's status updates (sent, delivered, failed, undelivered) +- **React to inbound messages**: Start a workflow whenever an SMS or MMS is received on a Twilio number +- **Access full message context**: Read sender/recipient details, message body, media attachments, and error codes from the triggering event + +In Sim, the Twilio triggers allow your agents to start workflows directly from Twilio messaging events. The Twilio Message Status trigger fires when a message's delivery status changes, exposing fields like `messageSid`, `smsStatus`, `messageStatus`, and `errorCode` so a workflow can react to delivery failures or confirmations. The Twilio SMS Received trigger fires on inbound SMS/MMS messages, exposing the sender and recipient numbers, message body, and any attached media, so a workflow can process incoming texts, route them, or trigger automated replies. +{/* MANUAL-CONTENT-END */} + ## Triggers A **Trigger** is a block that starts a workflow when an event happens in this service. diff --git a/apps/docs/content/docs/en/integrations/uptimerobot.mdx b/apps/docs/content/docs/en/integrations/uptimerobot.mdx index eb875883b30..bb541e6d41e 100644 --- a/apps/docs/content/docs/en/integrations/uptimerobot.mdx +++ b/apps/docs/content/docs/en/integrations/uptimerobot.mdx @@ -10,6 +10,21 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#111921" /> +{/* MANUAL-CONTENT-START:intro */} +[UptimeRobot](https://uptimerobot.com/) is a website and API monitoring service that tracks the availability of servers, endpoints, and heartbeat checks, alerting you when something goes down. It supports HTTP, keyword, ping, port, heartbeat, DNS, API, and UDP monitors, and can publish public status pages to keep users informed during incidents. + +With UptimeRobot, you can: + +- **Monitor uptime**: Create, update, pause, resume, and delete monitors across multiple check types +- **Track incidents**: List and inspect incidents, including root cause details like HTTP response codes +- **Schedule maintenance windows**: Suppress alerts during planned downtime, with one-time or recurring schedules +- **Manage alert contacts**: Create, retrieve, and delete email alert contacts for notifications +- **Publish status pages**: Create and update public status pages, optionally with a custom domain, logo, and icon + +In Sim, the UptimeRobot integration allows your agents to check monitor status, list and investigate incidents, create or update monitors and maintenance windows, manage alert contacts, and publish status pages—all through the UptimeRobot v3 API. This enables workflows that react to downtime, automate incident triage, schedule maintenance around deployments, and keep public status pages current without manual intervention. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate UptimeRobot into your workflow. Create and manage monitors, inspect incidents, schedule maintenance windows, manage alert contacts, and publish public status pages using the UptimeRobot v3 API. diff --git a/apps/docs/content/docs/en/integrations/workday.mdx b/apps/docs/content/docs/en/integrations/workday.mdx index 35652e80e9b..32e46699600 100644 --- a/apps/docs/content/docs/en/integrations/workday.mdx +++ b/apps/docs/content/docs/en/integrations/workday.mdx @@ -10,6 +10,22 @@ import { BlockInfoCard } from "@/components/ui/block-info-card" color="#F5F0EB" /> +{/* MANUAL-CONTENT-START:intro */} +[Workday](https://www.workday.com/) is a cloud-based Human Capital Management (HCM) and finance system used by organizations to manage their workforce, from hiring through termination. It centralizes worker records, organizational structure, compensation, and HR business processes. + +With this integration, you can: + +- **Manage worker records**: Retrieve individual worker profiles or list and search workers with pagination +- **Run the hire lifecycle**: Create pre-hire records and convert them into active employees with position and start date +- **Update worker data**: Change fields on existing worker records, such as business title or work email +- **Handle job and org changes**: Process transfers, promotions, demotions, and lateral moves, and retrieve organizations, departments, and cost centers +- **Manage onboarding and compensation**: Assign onboarding plans and retrieve compensation plan details for a worker +- **Process terminations**: Initiate the termination business process with a reason and effective date + +In Sim, the Workday integration allows your agents to look up and update worker profiles, create pre-hires and hire them into positions, assign onboarding plans, process job changes and terminations, and pull organization and compensation data—all through Workday's Integration System User authentication. This lets your agents automate HR operations such as onboarding new employees, keeping worker records current, and managing the employee lifecycle directly from a workflow. +{/* MANUAL-CONTENT-END */} + + ## Usage Instructions Integrate Workday HRIS into your workflow. Create pre-hires, hire employees, manage worker profiles, assign onboarding plans, handle job changes, retrieve compensation data, and process terminations. diff --git a/apps/docs/public/favicon/android-chrome-192x192.png b/apps/docs/public/favicon/android-chrome-192x192.png index 891e730eabf..01fa63be6f0 100644 Binary files a/apps/docs/public/favicon/android-chrome-192x192.png and b/apps/docs/public/favicon/android-chrome-192x192.png differ diff --git a/apps/docs/public/favicon/android-chrome-512x512.png b/apps/docs/public/favicon/android-chrome-512x512.png index e22c3b295b0..70db080feed 100644 Binary files a/apps/docs/public/favicon/android-chrome-512x512.png and b/apps/docs/public/favicon/android-chrome-512x512.png differ diff --git a/apps/docs/public/favicon/apple-touch-icon.png b/apps/docs/public/favicon/apple-touch-icon.png index a09d065ec40..0a9d90cd818 100644 Binary files a/apps/docs/public/favicon/apple-touch-icon.png and b/apps/docs/public/favicon/apple-touch-icon.png differ diff --git a/apps/docs/public/favicon/favicon-16x16.png b/apps/docs/public/favicon/favicon-16x16.png index 4ac7ae4717e..5b907892e13 100644 Binary files a/apps/docs/public/favicon/favicon-16x16.png and b/apps/docs/public/favicon/favicon-16x16.png differ diff --git a/apps/docs/public/favicon/favicon-32x32.png b/apps/docs/public/favicon/favicon-32x32.png index ee774f542d2..289d9bcb15f 100644 Binary files a/apps/docs/public/favicon/favicon-32x32.png and b/apps/docs/public/favicon/favicon-32x32.png differ diff --git a/apps/docs/public/favicon/favicon-96x96.png b/apps/docs/public/favicon/favicon-96x96.png index 34d58ba41d0..b32f9af3737 100644 Binary files a/apps/docs/public/favicon/favicon-96x96.png and b/apps/docs/public/favicon/favicon-96x96.png differ diff --git a/apps/docs/public/favicon/web-app-manifest-192x192.png b/apps/docs/public/favicon/web-app-manifest-192x192.png index ca2cabd6df9..01fa63be6f0 100644 Binary files a/apps/docs/public/favicon/web-app-manifest-192x192.png and b/apps/docs/public/favicon/web-app-manifest-192x192.png differ diff --git a/apps/docs/public/favicon/web-app-manifest-512x512.png b/apps/docs/public/favicon/web-app-manifest-512x512.png index aceecf70b33..70db080feed 100644 Binary files a/apps/docs/public/favicon/web-app-manifest-512x512.png and b/apps/docs/public/favicon/web-app-manifest-512x512.png differ diff --git a/apps/docs/public/icon.svg b/apps/docs/public/icon.svg index f96f875249b..d1b94a8d2e1 100644 --- a/apps/docs/public/icon.svg +++ b/apps/docs/public/icon.svg @@ -1 +1 @@ - \ No newline at end of file + diff --git a/apps/sim/blocks/blocks/context_dev.ts b/apps/sim/blocks/blocks/context_dev.ts index 07e00d910f2..f06ec1bb53c 100644 --- a/apps/sim/blocks/blocks/context_dev.ts +++ b/apps/sim/blocks/blocks/context_dev.ts @@ -14,15 +14,7 @@ const URL_OPS = [ 'extract_product', ] /** Operations whose primary input is a bare domain. */ -const DOMAIN_OPS = [ - 'map', - 'get_brand', - 'get_brand_simplified', - 'extract_products', - 'scrape_fonts', - 'scrape_styleguide', - 'prefetch_domain', -] +const DOMAIN_OPS = ['map', 'get_brand', 'extract_products', 'scrape_fonts', 'scrape_styleguide'] /** Classification operations keyed on a domain-or-name input. */ const CLASSIFY_OPS = ['classify_naics', 'classify_sic'] /** Brand operations that accept language/speed tuning. */ @@ -49,7 +41,6 @@ const MAX_AGE_OPS = [ 'get_brand_by_name', 'get_brand_by_email', 'get_brand_by_ticker', - 'get_brand_simplified', ] /** Operations that accept a post-load browser wait. */ const WAIT_FOR_OPS = ['scrape_markdown', 'scrape_html', 'scrape_images', 'screenshot', 'crawl'] @@ -118,10 +109,7 @@ export const ContextDevBlock: BlockConfig = { { label: 'Get Brand by Name', id: 'get_brand_by_name' }, { label: 'Get Brand by Email', id: 'get_brand_by_email' }, { label: 'Get Brand by Ticker', id: 'get_brand_by_ticker' }, - { label: 'Get Brand (Simplified)', id: 'get_brand_simplified' }, { label: 'Identify Transaction', id: 'identify_transaction' }, - { label: 'Prefetch Domain', id: 'prefetch_domain' }, - { label: 'Prefetch by Email', id: 'prefetch_by_email' }, ], value: () => 'scrape_markdown', }, @@ -170,8 +158,8 @@ export const ContextDevBlock: BlockConfig = { title: 'Work Email', type: 'short-input', placeholder: 'name@company.com', - condition: { field: 'operation', value: ['get_brand_by_email', 'prefetch_by_email'] }, - required: { field: 'operation', value: ['get_brand_by_email', 'prefetch_by_email'] }, + condition: { field: 'operation', value: 'get_brand_by_email' }, + required: { field: 'operation', value: 'get_brand_by_email' }, }, { id: 'ticker', @@ -563,10 +551,7 @@ Do not include any explanations, markdown formatting, or other text outside the 'context_dev_get_brand_by_name', 'context_dev_get_brand_by_email', 'context_dev_get_brand_by_ticker', - 'context_dev_get_brand_simplified', 'context_dev_identify_transaction', - 'context_dev_prefetch_domain', - 'context_dev_prefetch_by_email', ], config: { tool: (params) => @@ -745,11 +730,6 @@ Do not include any explanations, markdown formatting, or other text outside the setNumber('maxAgeMs') setNumber('timeoutMS') break - case 'get_brand_simplified': - setString('domain') - setNumber('maxAgeMs') - setNumber('timeoutMS') - break case 'identify_transaction': setString('transactionInfo') setString('countryGl') @@ -761,14 +741,6 @@ Do not include any explanations, markdown formatting, or other text outside the setBool('maxSpeed') setNumber('timeoutMS') break - case 'prefetch_domain': - setString('domain') - setNumber('timeoutMS') - break - case 'prefetch_by_email': - setString('email') - setNumber('timeoutMS') - break } return result @@ -783,7 +755,7 @@ Do not include any explanations, markdown formatting, or other text outside the input: { type: 'string', description: 'Domain or company name for classification' }, query: { type: 'string', description: 'Web search query' }, name: { type: 'string', description: 'Company name for brand lookup' }, - email: { type: 'string', description: 'Work email for brand lookup or prefetch' }, + email: { type: 'string', description: 'Work email for brand lookup' }, ticker: { type: 'string', description: 'Stock ticker for brand lookup' }, transactionInfo: { type: 'string', description: 'Transaction descriptor to identify' }, schema: { type: 'json', description: 'JSON schema for structured extraction' }, @@ -850,7 +822,6 @@ Do not include any explanations, markdown formatting, or other text outside the meta: { type: 'json', description: 'Sitemap discovery stats' }, query: { type: 'string', description: 'The query that was searched' }, status: { type: 'string', description: 'Operation status' }, - message: { type: 'string', description: 'Prefetch result message' }, urlsAnalyzed: { type: 'json', description: 'URLs analyzed during extraction' }, data: { type: 'json', description: 'Structured data extracted from the site' }, isProductPage: { type: 'boolean', description: 'Whether the URL is a product page' }, diff --git a/apps/sim/lib/integrations/integrations.json b/apps/sim/lib/integrations/integrations.json index 85d9aaf86b1..98849d6a9a4 100644 --- a/apps/sim/lib/integrations/integrations.json +++ b/apps/sim/lib/integrations/integrations.json @@ -1,5 +1,5 @@ { - "updatedAt": "2026-07-10", + "updatedAt": "2026-07-11", "integrations": [ { "type": "onepassword", @@ -3870,24 +3870,12 @@ "name": "Get Brand by Ticker", "description": "Retrieve brand data for a public company by its stock ticker symbol." }, - { - "name": "Get Brand (Simplified)", - "description": "Retrieve essential brand data for a domain: title, colors, logos, and backdrops." - }, { "name": "Identify Transaction", "description": "Identify the brand behind a raw bank/card transaction descriptor and return its brand data." - }, - { - "name": "Prefetch Domain", - "description": "Queue a domain for brand-data prefetching to reduce latency on later requests (subscribers; 0 credits)." - }, - { - "name": "Prefetch by Email", - "description": "Queue an email's domain for brand-data prefetching to reduce later latency (subscribers; 0 credits). Free/disposable emails are rejected." } ], - "operationCount": 22, + "operationCount": 19, "triggers": [], "triggerCount": 0, "authType": "api-key", diff --git a/apps/sim/tools/context_dev/get_brand_simplified.ts b/apps/sim/tools/context_dev/get_brand_simplified.ts deleted file mode 100644 index 1f01f0aa800..00000000000 --- a/apps/sim/tools/context_dev/get_brand_simplified.ts +++ /dev/null @@ -1,81 +0,0 @@ -import { contextDevHosting } from '@/tools/context_dev/hosting' -import type { - ContextDevGetBrandSimplifiedParams, - ContextDevGetBrandSimplifiedResponse, -} from '@/tools/context_dev/types' -import { SIMPLIFIED_BRAND_OUTPUT_PROPERTIES } from '@/tools/context_dev/types' -import { - appendParam, - CONTEXT_DEV_BASE_URL, - CREDIT_OUTPUTS, - contextDevHeaders, - parseContextDevResponse, - transformBrandResponse, -} from '@/tools/context_dev/utils' -import type { ToolConfig } from '@/tools/types' - -export const contextDevGetBrandSimplifiedTool: ToolConfig< - ContextDevGetBrandSimplifiedParams, - ContextDevGetBrandSimplifiedResponse -> = { - id: 'context_dev_get_brand_simplified', - name: 'Context.dev Get Brand (Simplified)', - description: 'Retrieve essential brand data for a domain: title, colors, logos, and backdrops.', - version: '1.0.0', - - hosting: contextDevHosting(), - - params: { - domain: { - type: 'string', - required: true, - visibility: 'user-or-llm', - description: 'The domain to retrieve simplified brand data for (e.g., "airbnb.com")', - }, - maxAgeMs: { - type: 'number', - required: false, - visibility: 'user-or-llm', - description: 'Cache max age in milliseconds (86400000-31536000000, default: 7776000000)', - }, - timeoutMS: { - type: 'number', - required: false, - visibility: 'user-or-llm', - description: 'Request timeout in milliseconds (1000-300000)', - }, - apiKey: { - type: 'string', - required: true, - visibility: 'user-only', - description: 'Context.dev API key', - }, - }, - - request: { - method: 'GET', - url: (params) => { - const url = new URL(`${CONTEXT_DEV_BASE_URL}/brand/retrieve-simplified`) - appendParam(url.searchParams, 'domain', params.domain) - appendParam(url.searchParams, 'maxAgeMs', params.maxAgeMs) - appendParam(url.searchParams, 'timeoutMS', params.timeoutMS) - return url.toString() - }, - headers: (params) => contextDevHeaders(params.apiKey), - }, - - transformResponse: async (response: Response) => { - const data = await parseContextDevResponse(response) - return { success: true, output: transformBrandResponse(data) } - }, - - outputs: { - status: { type: 'string', description: 'Retrieval status' }, - brand: { - type: 'object', - description: 'Simplified brand data (domain, title, colors, logos, backdrops)', - properties: SIMPLIFIED_BRAND_OUTPUT_PROPERTIES, - }, - ...CREDIT_OUTPUTS, - }, -} diff --git a/apps/sim/tools/context_dev/index.ts b/apps/sim/tools/context_dev/index.ts index 9848723ebf3..093fa5ca81c 100644 --- a/apps/sim/tools/context_dev/index.ts +++ b/apps/sim/tools/context_dev/index.ts @@ -8,11 +8,8 @@ export { contextDevGetBrandTool } from '@/tools/context_dev/get_brand' export { contextDevGetBrandByEmailTool } from '@/tools/context_dev/get_brand_by_email' export { contextDevGetBrandByNameTool } from '@/tools/context_dev/get_brand_by_name' export { contextDevGetBrandByTickerTool } from '@/tools/context_dev/get_brand_by_ticker' -export { contextDevGetBrandSimplifiedTool } from '@/tools/context_dev/get_brand_simplified' export { contextDevIdentifyTransactionTool } from '@/tools/context_dev/identify_transaction' export { contextDevMapTool } from '@/tools/context_dev/map' -export { contextDevPrefetchByEmailTool } from '@/tools/context_dev/prefetch_by_email' -export { contextDevPrefetchDomainTool } from '@/tools/context_dev/prefetch_domain' export { contextDevScrapeFontsTool } from '@/tools/context_dev/scrape_fonts' export { contextDevScrapeHtmlTool } from '@/tools/context_dev/scrape_html' export { contextDevScrapeImagesTool } from '@/tools/context_dev/scrape_images' diff --git a/apps/sim/tools/context_dev/prefetch_by_email.ts b/apps/sim/tools/context_dev/prefetch_by_email.ts deleted file mode 100644 index 5a682df6966..00000000000 --- a/apps/sim/tools/context_dev/prefetch_by_email.ts +++ /dev/null @@ -1,78 +0,0 @@ -import { contextDevHosting } from '@/tools/context_dev/hosting' -import type { - ContextDevPrefetchByEmailParams, - ContextDevPrefetchResponse, -} from '@/tools/context_dev/types' -import { - CONTEXT_DEV_BASE_URL, - CREDIT_OUTPUTS, - contextDevJsonHeaders, - extractCreditMetadata, - parseContextDevResponse, -} from '@/tools/context_dev/utils' -import type { ToolConfig } from '@/tools/types' - -export const contextDevPrefetchByEmailTool: ToolConfig< - ContextDevPrefetchByEmailParams, - ContextDevPrefetchResponse -> = { - id: 'context_dev_prefetch_by_email', - name: 'Context.dev Prefetch by Email', - description: - "Queue an email's domain for brand-data prefetching to reduce later latency (subscribers; 0 credits). Free/disposable emails are rejected.", - version: '1.0.0', - - hosting: contextDevHosting(), - - params: { - email: { - type: 'string', - required: true, - visibility: 'user-or-llm', - description: 'Work email address whose domain should be prefetched (free providers rejected)', - }, - timeoutMS: { - type: 'number', - required: false, - visibility: 'user-or-llm', - description: 'Request timeout in milliseconds (1000-300000)', - }, - apiKey: { - type: 'string', - required: true, - visibility: 'user-only', - description: 'Context.dev API key', - }, - }, - - request: { - method: 'POST', - url: () => `${CONTEXT_DEV_BASE_URL}/brand/prefetch-by-email`, - headers: (params) => contextDevJsonHeaders(params.apiKey), - body: (params) => { - const body: Record = { email: params.email } - if (params.timeoutMS != null) body.timeoutMS = params.timeoutMS - return body - }, - }, - - transformResponse: async (response: Response) => { - const data = await parseContextDevResponse(response) - return { - success: true, - output: { - status: data.status ?? '', - message: data.message ?? '', - domain: data.domain ?? '', - ...extractCreditMetadata(data.key_metadata), - }, - } - }, - - outputs: { - status: { type: 'string', description: 'Prefetch status' }, - message: { type: 'string', description: 'Human-readable prefetch result message' }, - domain: { type: 'string', description: 'The domain queued for prefetching' }, - ...CREDIT_OUTPUTS, - }, -} diff --git a/apps/sim/tools/context_dev/prefetch_domain.ts b/apps/sim/tools/context_dev/prefetch_domain.ts deleted file mode 100644 index 32420195669..00000000000 --- a/apps/sim/tools/context_dev/prefetch_domain.ts +++ /dev/null @@ -1,78 +0,0 @@ -import { contextDevHosting } from '@/tools/context_dev/hosting' -import type { - ContextDevPrefetchDomainParams, - ContextDevPrefetchResponse, -} from '@/tools/context_dev/types' -import { - CONTEXT_DEV_BASE_URL, - CREDIT_OUTPUTS, - contextDevJsonHeaders, - extractCreditMetadata, - parseContextDevResponse, -} from '@/tools/context_dev/utils' -import type { ToolConfig } from '@/tools/types' - -export const contextDevPrefetchDomainTool: ToolConfig< - ContextDevPrefetchDomainParams, - ContextDevPrefetchResponse -> = { - id: 'context_dev_prefetch_domain', - name: 'Context.dev Prefetch Domain', - description: - 'Queue a domain for brand-data prefetching to reduce latency on later requests (subscribers; 0 credits).', - version: '1.0.0', - - hosting: contextDevHosting(), - - params: { - domain: { - type: 'string', - required: true, - visibility: 'user-or-llm', - description: 'The domain to prefetch brand data for (e.g., "example.com")', - }, - timeoutMS: { - type: 'number', - required: false, - visibility: 'user-or-llm', - description: 'Request timeout in milliseconds (1000-300000)', - }, - apiKey: { - type: 'string', - required: true, - visibility: 'user-only', - description: 'Context.dev API key', - }, - }, - - request: { - method: 'POST', - url: () => `${CONTEXT_DEV_BASE_URL}/brand/prefetch`, - headers: (params) => contextDevJsonHeaders(params.apiKey), - body: (params) => { - const body: Record = { domain: params.domain } - if (params.timeoutMS != null) body.timeoutMS = params.timeoutMS - return body - }, - }, - - transformResponse: async (response: Response) => { - const data = await parseContextDevResponse(response) - return { - success: true, - output: { - status: data.status ?? '', - message: data.message ?? '', - domain: data.domain ?? '', - ...extractCreditMetadata(data.key_metadata), - }, - } - }, - - outputs: { - status: { type: 'string', description: 'Prefetch status' }, - message: { type: 'string', description: 'Human-readable prefetch result message' }, - domain: { type: 'string', description: 'The domain queued for prefetching' }, - ...CREDIT_OUTPUTS, - }, -} diff --git a/apps/sim/tools/context_dev/types.ts b/apps/sim/tools/context_dev/types.ts index 564a66b8aba..5bf9b823aa5 100644 --- a/apps/sim/tools/context_dev/types.ts +++ b/apps/sim/tools/context_dev/types.ts @@ -326,41 +326,6 @@ export interface ContextDevIdentifyTransactionParams { timeoutMS?: number } -export interface ContextDevGetBrandSimplifiedParams { - apiKey: string - domain: string - maxAgeMs?: number - timeoutMS?: number -} - -export interface ContextDevGetBrandSimplifiedResponse extends ToolResponse { - output: CreditFields & { - status: string - brand: Record | null - } -} - -export interface ContextDevPrefetchByEmailParams { - apiKey: string - email: string - timeoutMS?: number -} - -export interface ContextDevPrefetchDomainParams { - apiKey: string - domain: string - timeoutMS?: number -} - -/** Shared response shape for the prefetch utility endpoints. */ -export interface ContextDevPrefetchResponse extends ToolResponse { - output: CreditFields & { - status: string - message: string - domain: string - } -} - /** Output schema for a single web search result. */ export const SEARCH_RESULT_OUTPUT_PROPERTIES = { url: { type: 'string', description: 'Result page URL' }, diff --git a/apps/sim/tools/registry.ts b/apps/sim/tools/registry.ts index 7f4a6c48674..e6f33250a0d 100644 --- a/apps/sim/tools/registry.ts +++ b/apps/sim/tools/registry.ts @@ -608,12 +608,9 @@ import { contextDevGetBrandByEmailTool, contextDevGetBrandByNameTool, contextDevGetBrandByTickerTool, - contextDevGetBrandSimplifiedTool, contextDevGetBrandTool, contextDevIdentifyTransactionTool, contextDevMapTool, - contextDevPrefetchByEmailTool, - contextDevPrefetchDomainTool, contextDevScrapeFontsTool, contextDevScrapeHtmlTool, contextDevScrapeImagesTool, @@ -6810,10 +6807,7 @@ export const tools: Record = { context_dev_get_brand_by_name: contextDevGetBrandByNameTool, context_dev_get_brand_by_email: contextDevGetBrandByEmailTool, context_dev_get_brand_by_ticker: contextDevGetBrandByTickerTool, - context_dev_get_brand_simplified: contextDevGetBrandSimplifiedTool, context_dev_identify_transaction: contextDevIdentifyTransactionTool, - context_dev_prefetch_domain: contextDevPrefetchDomainTool, - context_dev_prefetch_by_email: contextDevPrefetchByEmailTool, cursor_list_agents: cursorListAgentsTool, cursor_list_agents_v2: cursorListAgentsV2Tool, cursor_get_agent: cursorGetAgentTool,