Skip to content

Commit 5bf21e5

Browse files
committed
chore(docs): normalize spacing from generate-docs pass
Ran the docs generator to verify our new intro sections survive regeneration cleanly. It reformats the blank line before "## Usage Instructions" to match every other manually-annotated page.
1 parent 802767e commit 5bf21e5

26 files changed

Lines changed: 26 additions & 0 deletions

apps/docs/content/docs/en/integrations/brandfetch.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ With Brandfetch, you can:
2323
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.
2424
{/* MANUAL-CONTENT-END */}
2525

26+
2627
## Usage Instructions
2728

2829
Integrate Brandfetch into your workflow. Retrieve brand logos, colors, fonts, and company data by domain, ticker, or name search.

apps/docs/content/docs/en/integrations/codepipeline.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ With this integration, you can:
2323
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.
2424
{/* MANUAL-CONTENT-END */}
2525

26+
2627
## Usage Instructions
2728

2829
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.

apps/docs/content/docs/en/integrations/context_dev.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ With Context.dev, you can:
2323
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.
2424
{/* MANUAL-CONTENT-END */}
2525

26+
2627
## Usage Instructions
2728

2829
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.

apps/docs/content/docs/en/integrations/crowdstrike.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ With this integration, you can:
2222
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.
2323
{/* MANUAL-CONTENT-END */}
2424

25+
2526
## Usage Instructions
2627

2728
Integrate CrowdStrike Identity Protection into workflows to search sensors, fetch documented sensor details by device ID, and run documented sensor aggregate queries.

apps/docs/content/docs/en/integrations/deployments.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ Deployments is Sim's built-in system for taking a workflow's draft state live fo
2020
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.
2121
{/* MANUAL-CONTENT-END */}
2222

23+
2324
## Usage Instructions
2425

2526
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.

apps/docs/content/docs/en/integrations/downdetector.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ With Downdetector, you can:
2323
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.
2424
{/* MANUAL-CONTENT-END */}
2525

26+
2627
## Usage Instructions
2728

2829
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.

apps/docs/content/docs/en/integrations/emailbison.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ With Email Bison, you can:
2323
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.
2424
{/* MANUAL-CONTENT-END */}
2525

26+
2627
## Usage Instructions
2728

2829
Integrate Email Bison into workflows. Create and update leads, manage campaigns, attach leads to campaigns, list replies, and organize leads with tags.

apps/docs/content/docs/en/integrations/enrichment.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ Data Enrichment is a built-in Sim block that looks up missing data — work emai
1616
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.
1717
{/* MANUAL-CONTENT-END */}
1818

19+
1920
## Usage Instructions
2021

2122
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.

apps/docs/content/docs/en/integrations/extend.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
1616
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.
1717
{/* MANUAL-CONTENT-END */}
1818

19+
1920
## Usage Instructions
2021

2122
Integrate Extend AI into the workflow. Parse and extract structured content from documents or file references.

apps/docs/content/docs/en/integrations/google_contacts.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ With this block, you can:
2222
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.
2323
{/* MANUAL-CONTENT-END */}
2424

25+
2526
## Usage Instructions
2627

2728
Integrate Google Contacts into the workflow. Can create, read, update, delete, list, and search contacts.

0 commit comments

Comments
 (0)