You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 192e65a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: apps/docs/EDITORIAL_GUIDE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ A link replaces repeated detail only after the owner contains it. Keep a concise
60
60
- Use a callout for a specific prerequisite or a non-obvious security, data-loss, or operational risk that deserves interruption. Use ordinary prose or a table for normal explanation. Keep important limits visible.
61
61
- Use Markdown lists and tables for simple procedures and reference data. Use tabs for distinct configurations and Steps for substantial sequential procedures.
62
62
- Integration table cells use ordinary word wrapping so short field names and types stay readable. Keep long tokens within the existing table scroll container; do not let them widen the page.
63
-
- On large integration references, keep action and trigger descriptions visible and fold their field tables into `ReferenceDetails`. Preserve headings inside each disclosure so direct links and browser search can reveal them. Setup requirements and consequential warnings stay outside the folded tables.
63
+
- On integration references, keep action and trigger descriptions visible and fold their field tables into `ReferenceDetails`, regardless of the number of fields. Preserve headings inside each disclosure so direct links and browser search can reveal them. Setup requirements and consequential warnings stay outside the folded tables.
64
64
- Integration logos belong beside the page title, using the generated `integration` frontmatter. Keep the regular docs header actions and do not repeat the logo in the article body.
65
65
- Match inline code to Sim Chat: normal-weight monospace text, tight padding, and the existing borderless filled surface tokens. Scope the treatment to prose code; preserve fenced examples, API route bars, schema controls, and selector labels.
66
66
- Use the shared `TabsSelect` control for API response and request-example pickers, with accessible names that include the current value, checked radio semantics for single choices, and menus aligned to their triggers. Keep docs pickers nonmodal so they do not hide lazily hydrating siblings. Keep response headings free of inherited extra margins. Scope dependency filter styling to `data-object-search-input`, including schema popovers portaled to the body; focus stays inside the field, and touch fields retain the shared target and text sizes.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/apify.mdx
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,13 @@ integration:
6
6
color: "#FFFFFF"
7
7
---
8
8
9
+
import { ReferenceDetails } from "@/components/ui/reference-details"
10
+
9
11
10
12
{/* MANUAL-CONTENT-START:intro */}
11
13
[Apify](https://apify.com/) runs Actors for web scraping and browser automation. Run an Actor synchronously when it can finish within the synchronous endpoint’s five-minute limit. **Run Actor (Async)** starts a provider run and polls it within the same Sim step; it does not return immediately for detached processing. Its polling budget follows Sim’s default synchronous execution timeout. If that wait ends before the Actor finishes, use the returned run ID with **Get Run**, then retrieve dataset items after success. You can also run saved Actor tasks and fetch dataset items directly.
12
14
{/* MANUAL-CONTENT-END */}
13
15
14
-
15
16
## Use the block [#usage-instructions]
16
17
17
18
Run any Apify actor or saved task with custom input, fetch dataset items, and check run status. Supports both synchronous and asynchronous execution with automatic dataset fetching.
@@ -22,6 +23,8 @@ Run any Apify actor or saved task with custom input, fetch dataset items, and ch
22
23
23
24
Run an APIFY actor synchronously and get results (max 5 minutes)
24
25
26
+
<ReferenceDetails>
27
+
25
28
#### Input
26
29
27
30
| Parameter | Type | Required | Description |
@@ -42,10 +45,14 @@ Run an APIFY actor synchronously and get results (max 5 minutes)
42
45
| `status` | string | Run status \(SUCCEEDED, FAILED, etc.\) |
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/arxiv.mdx
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,13 @@ integration:
6
6
color: "#FFFFFF"
7
7
---
8
8
9
+
import { ReferenceDetails } from "@/components/ui/reference-details"
10
+
9
11
10
12
{/* MANUAL-CONTENT-START:intro */}
11
13
[arXiv](https://arxiv.org/) hosts research papers. Search by keyword, author, title, or category, retrieve a paper’s metadata, or list papers by an author. This integration does not require an API key or OAuth connection.
12
14
{/* MANUAL-CONTENT-END */}
13
15
14
-
15
16
## Use the block [#usage-instructions]
16
17
17
18
Search arXiv papers, retrieve paper metadata, or list an author’s papers. No API key or OAuth connection is required.
@@ -22,6 +23,8 @@ Search arXiv papers, retrieve paper metadata, or list an author’s papers. No A
22
23
23
24
Search for academic papers on ArXiv by keywords, authors, titles, or other fields.
24
25
26
+
<ReferenceDetails>
27
+
25
28
#### Input
26
29
27
30
| Parameter | Type | Required | Description |
@@ -39,10 +42,14 @@ Search for academic papers on ArXiv by keywords, authors, titles, or other field
39
42
| `papers` | json | Array of papers matching the search query |
40
43
| `totalResults` | number | Total number of results found for the search query |
41
44
45
+
</ReferenceDetails>
46
+
42
47
### ArXiv Get Paper
43
48
44
49
Get detailed information about a specific ArXiv paper by its ID.
45
50
51
+
<ReferenceDetails>
52
+
46
53
#### Input
47
54
48
55
| Parameter | Type | Required | Description |
@@ -55,10 +62,14 @@ Get detailed information about a specific ArXiv paper by its ID.
55
62
| --------- | ---- | ----------- |
56
63
| `paper` | json | Detailed information about the requested ArXiv paper |
57
64
65
+
</ReferenceDetails>
66
+
58
67
### ArXiv Get Author Papers
59
68
60
69
Search for papers by a specific author on ArXiv.
61
70
71
+
<ReferenceDetails>
72
+
62
73
#### Input
63
74
64
75
| Parameter | Type | Required | Description |
@@ -73,4 +84,6 @@ Search for papers by a specific author on ArXiv.
73
84
| `authorPapers` | json | Array of papers authored by the specified author |
74
85
| `totalResults` | number | Total number of papers found for the author |
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/clay.mdx
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,13 @@ integration:
6
6
color: "#FFFFFF"
7
7
---
8
8
9
+
import { ReferenceDetails } from "@/components/ui/reference-details"
10
+
9
11
10
12
{/* MANUAL-CONTENT-START:intro */}
11
13
[Clay](https://www.clay.com/) organizes and enriches data in tables. Use the Clay Populate action to send structured data from your Sim workflow to a Clay table through its webhook URL—for example, lead records or research results.
12
14
{/* MANUAL-CONTENT-END */}
13
15
14
-
15
16
## Use the block [#usage-instructions]
16
17
17
18
Send structured records to a Clay table through its webhook URL.
@@ -22,6 +23,8 @@ Send structured records to a Clay table through its webhook URL.
22
23
23
24
Send structured JSON data to a Clay table webhook and return its response and HTTP metadata.
24
25
26
+
<ReferenceDetails>
27
+
25
28
#### Input
26
29
27
30
| Parameter | Type | Required | Description |
@@ -42,4 +45,6 @@ Send structured JSON data to a Clay table webhook and return its response and HT
42
45
| ↳ `timestamp` | string | ISO timestamp recorded when the webhook response was processed |
43
46
| ↳ `contentType` | string | Content type of the response |
| `catchAll` | boolean | Whether the domain is catch-all |
49
51
52
+
</ReferenceDetails>
53
+
50
54
### Datagma Enrich Person
51
55
52
56
Enrich a person's profile using their email, LinkedIn URL, or full name and company. Returns job title, company, location, and social data. Uses 2 credits per match; add 30 credits when a phone number is found.
@@ -92,6 +96,8 @@ Enrich a person's profile using their email, LinkedIn URL, or full name and comp
92
96
93
97
Enrich a company profile using a domain, company name, or SIREN number (France). Returns size, industry, revenue, and description. Uses 2 credits per match.
94
98
99
+
<ReferenceDetails>
100
+
95
101
#### Input
96
102
97
103
| Parameter | Type | Required | Description |
@@ -115,10 +121,14 @@ Enrich a company profile using a domain, company name, or SIREN number (France).
115
121
| `revenueRange` | string | Estimated annual revenue range |
0 commit comments