added more wandConfigs

Author: waleedlatif1

apps/sim/blocks/blocks/airtable.ts

@@ -79,6 +79,37 @@ export const AirtableBlock: BlockConfig<AirtableResponse> = {
       type: 'long-input',
       placeholder: 'Airtable formula to filter records (optional)',
       condition: { field: 'operation', value: 'list' },
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate an Airtable filter formula based on the user's description.
+Airtable formulas use a syntax similar to Excel/spreadsheet formulas.
+
+Common functions:
+- {Field Name} - Reference a field by name (with curly braces)
+- AND(condition1, condition2) - Both conditions must be true
+- OR(condition1, condition2) - Either condition can be true
+- NOT(condition) - Negates the condition
+- IF(condition, value_if_true, value_if_false)
+- FIND("text", {Field}) - Find text in a field (returns position or 0)
+- SEARCH("text", {Field}) - Case-insensitive search
+- LEN({Field}) - Length of text
+- DATETIME_DIFF(date1, date2, 'days') - Difference between dates
+- TODAY() - Current date
+- NOW() - Current date and time
+- BLANK() - Empty value
+- {Field} = "" - Check if field is empty
+- {Field} != "" - Check if field is not empty
+
+Examples:
+- "find all completed tasks" -> {Status} = "Completed"
+- "records from last 7 days" -> DATETIME_DIFF(NOW(), {Created}, 'days') <= 7
+- "name contains John" -> FIND("John", {Name}) > 0
+- "status is active or pending" -> OR({Status} = "Active", {Status} = "Pending")
+- "priority is high and not assigned" -> AND({Priority} = "High", {Assignee} = "")
+
+Return ONLY the formula - no explanations, no quotes around the entire formula.`,
+        placeholder: 'Describe the filter criteria (e.g., "completed tasks from last week")...',
+      },
     },
     {
       id: 'records',
@@ -87,6 +118,44 @@ export const AirtableBlock: BlockConfig<AirtableResponse> = {
       placeholder: 'For Create: `[{ "fields": { ... } }]`\n',
       condition: { field: 'operation', value: ['create', 'updateMultiple'] },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate an Airtable records JSON array based on the user's description.
+The array should contain objects with a "fields" property containing the record data.
+
+Current records: {context}
+
+Format:
+[
+  {
+    "fields": {
+      "Field Name": "value",
+      "Another Field": "another value"
+    }
+  }
+]
+
+For updates, include the record ID:
+[
+  {
+    "id": "recXXXXXXXXXXXXXX",
+    "fields": {
+      "Field Name": "updated value"
+    }
+  }
+]
+
+Examples:
+- "add a task called 'Review PR' with status 'Pending'" ->
+[{"fields": {"Name": "Review PR", "Status": "Pending"}}]
+
+- "create 3 contacts: John, Jane, Bob" ->
+[{"fields": {"Name": "John"}}, {"fields": {"Name": "Jane"}}, {"fields": {"Name": "Bob"}}]
+
+Return ONLY the valid JSON array - no explanations, no markdown.`,
+        placeholder: 'Describe the records to create or update...',
+        generationType: 'json-object',
+      },
     },
     {
       id: 'fields',
@@ -95,6 +164,32 @@ export const AirtableBlock: BlockConfig<AirtableResponse> = {
       placeholder: 'Fields to update: `{ "Field Name": "New Value" }`',
       condition: { field: 'operation', value: 'update' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate an Airtable fields JSON object based on the user's description.
+The object should contain field names as keys and their values.
+
+Current fields: {context}
+
+Format:
+{
+  "Field Name": "value",
+  "Another Field": "another value",
+  "Number Field": 123,
+  "Checkbox Field": true
+}
+
+Examples:
+- "set status to completed and priority to low" ->
+{"Status": "Completed", "Priority": "Low"}
+
+- "update the name to 'New Project' and set the due date" ->
+{"Name": "New Project", "Due Date": "2024-12-31"}
+
+Return ONLY the valid JSON object - no explanations, no markdown.`,
+        placeholder: 'Describe the fields to update...',
+        generationType: 'json-object',
+      },
     },
     ...getTrigger('airtable_webhook').subBlocks,
   ],

apps/sim/blocks/blocks/apify.ts

@@ -46,6 +46,32 @@ export const ApifyBlock: BlockConfig<RunActorResult> = {
       language: 'json',
       placeholder: '{\n  "startUrl": "https://example.com",\n  "maxPages": 10\n}',
       required: false,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a JSON configuration object for an Apify actor based on the user's description.
+Apify actors typically accept configuration for web scraping, automation, or data processing tasks.
+
+Current input: {context}
+
+Common Apify actor input patterns:
+- Web scrapers: startUrls, maxPages, proxyConfiguration
+- Crawlers: startUrls, maxRequestsPerCrawl, maxConcurrency
+- Data processors: inputData, outputFormat, filters
+
+Examples:
+- "scrape 5 pages starting from example.com" ->
+{"startUrls": [{"url": "https://example.com"}], "maxPages": 5}
+
+- "crawl the site with proxy and limit to 100 requests" ->
+{"startUrls": [{"url": "https://example.com"}], "maxRequestsPerCrawl": 100, "proxyConfiguration": {"useApifyProxy": true}}
+
+- "extract product data with custom selectors" ->
+{"startUrls": [{"url": "https://shop.example.com"}], "selectors": {"title": "h1.product-title", "price": ".price"}}
+
+Return ONLY the valid JSON object - no explanations, no markdown.`,
+        placeholder: 'Describe the actor configuration you need...',
+        generationType: 'json-object',
+      },
     },
     {
       id: 'timeout',

apps/sim/blocks/blocks/clay.ts

@@ -30,6 +30,14 @@ export const ClayBlock: BlockConfig<ClayPopulateResponse> = {
 JSON: Best for populating multiple columns.
 Plain Text: Best for populating a table in free-form style.
       `,
+      wandConfig: {
+        enabled: true,
+        prompt:
+          'Generate JSON data structure or plain text content based on the user description. For JSON, create a well-structured object or array with appropriate keys and sample values. Return ONLY the data content - no explanations, no extra formatting.',
+        placeholder:
+          'Describe the data structure you need (e.g., "array of contacts with name, email, and company")...',
+        generationType: 'json-object',
+      },
     },
     {
       id: 'authToken',

apps/sim/blocks/blocks/datadog.ts

@@ -54,6 +54,19 @@ export const DatadogBlock: BlockConfig<DatadogResponse> = {
 ]`,
       condition: { field: 'operation', value: 'datadog_submit_metrics' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a JSON array of Datadog metrics based on the user's description.
+Each metric object should have:
+- "metric": The metric name (e.g., "custom.app.response_time")
+- "type": The metric type ("gauge", "count", or "rate")
+- "points": Array of {timestamp, value} objects
+- "tags": Array of tag strings (e.g., "env:production")
+
+Return ONLY valid JSON - no explanations, no markdown code blocks.`,
+        placeholder: 'Describe the metrics you want to submit...',
+        generationType: 'json-object',
+      },
     },
 
     // ========================
@@ -66,6 +79,18 @@ export const DatadogBlock: BlockConfig<DatadogResponse> = {
       placeholder: 'avg:system.cpu.user{*}',
       condition: { field: 'operation', value: 'datadog_query_timeseries' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a Datadog metrics query based on the user's description.
+The query format is: <aggregation>:<metric_name>{<tag_filters>}
+Examples:
+- "avg:system.cpu.user{*}" - Average CPU usage across all hosts
+- "sum:app.requests{env:production} by {service}" - Sum of requests grouped by service
+- "max:system.mem.used{host:webserver-1}" - Max memory on specific host
+
+Return ONLY the query string - no explanations, no quotes around the entire query.`,
+        placeholder: 'Describe what metrics you want to query...',
+      },
     },
     {
       id: 'from',
@@ -120,6 +145,15 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       placeholder: 'Deployment completed',
       condition: { field: 'operation', value: 'datadog_create_event' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a concise, descriptive event title for Datadog based on the user's description.
+The title should be short (under 100 characters), clear, and action-oriented.
+Examples: "Deployment completed", "High CPU usage detected", "Service restart initiated"
+
+Return ONLY the title text - no quotes, no extra formatting.`,
+        placeholder: 'Describe the event you want to create...',
+      },
     },
     {
       id: 'text',
@@ -128,6 +162,15 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       placeholder: 'Describe the event...',
       condition: { field: 'operation', value: 'datadog_create_event' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate descriptive event text for a Datadog event based on the user's description.
+Include relevant details like what happened, when, and any important context.
+Can use Markdown formatting for readability.
+
+Return the event description text directly - no extra formatting needed.`,
+        placeholder: 'Describe the event details...',
+      },
     },
     {
       id: 'alertType',
@@ -171,6 +214,15 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       placeholder: 'High CPU Usage Alert',
       condition: { field: 'operation', value: 'datadog_create_monitor' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a clear, descriptive monitor name for Datadog based on the user's description.
+The name should be concise but descriptive, indicating what is being monitored.
+Examples: "High CPU Usage Alert", "Database Connection Pool Low", "API Error Rate Spike"
+
+Return ONLY the monitor name - no quotes, no extra formatting.`,
+        placeholder: 'Describe what the monitor should track...',
+      },
     },
     {
       id: 'type',
@@ -196,13 +248,36 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       placeholder: 'avg(last_5m):avg:system.cpu.idle{*} < 20',
       condition: { field: 'operation', value: 'datadog_create_monitor' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a Datadog monitor query based on the user's description.
+Monitor query format: <aggregation>(<time_window>):<metric_query> <comparator> <threshold>
+Examples:
+- "avg(last_5m):avg:system.cpu.idle{*} < 20" - Alert when average CPU idle is below 20%
+- "sum(last_1h):sum:app.errors{env:production} > 100" - Alert when errors exceed 100 in an hour
+- "max(last_15m):max:system.disk.used{*} by {host} > 90" - Alert when disk usage exceeds 90%
+
+Return ONLY the monitor query string - no explanations.`,
+        placeholder: 'Describe what condition should trigger the alert...',
+      },
     },
     {
       id: 'message',
       title: 'Notification Message',
       type: 'long-input',
       placeholder: 'Alert! CPU usage is high. @slack-alerts',
       condition: { field: 'operation', value: 'datadog_create_monitor' },
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a Datadog monitor notification message based on the user's description.
+The message should include:
+- A clear description of what triggered the alert
+- Relevant template variables like {{host.name}}, {{value}}
+- Optional: notification handles like @slack-channel or @pagerduty
+
+Return the notification message text directly.`,
+        placeholder: 'Describe what the notification should say...',
+      },
     },
     {
       id: 'monitorTags',
@@ -224,6 +299,20 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       type: 'code',
       placeholder: '{"notify_no_data": true, "thresholds": {"critical": 90}}',
       condition: { field: 'operation', value: 'datadog_create_monitor' },
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate Datadog monitor options JSON based on the user's description.
+Common options include:
+- "notify_no_data": boolean - Notify when data stops arriving
+- "thresholds": {"critical": number, "warning": number} - Alert thresholds
+- "renotify_interval": number - Minutes between re-notifications
+- "timeout_h": number - Hours before auto-resolving
+- "include_tags": boolean - Include trigger tags in notifications
+
+Return ONLY valid JSON - no explanations, no markdown code blocks.`,
+        placeholder: 'Describe the monitor options you need...',
+        generationType: 'json-object',
+      },
     },
 
     // ========================
@@ -305,6 +394,18 @@ Return ONLY the numeric timestamp - no explanations, no quotes, no extra text.`,
       placeholder: 'service:web-app status:error',
       condition: { field: 'operation', value: 'datadog_query_logs' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a Datadog log search query based on the user's description.
+The query uses facet syntax: facet:value
+Examples:
+- "service:web-app status:error" - Errors from web-app service
+- "source:nginx @http.status_code:>=500" - Nginx 5xx errors
+- "host:prod-* @duration:>1000" - Slow requests on prod hosts
+
+Return ONLY the search query string - no explanations.`,
+        placeholder: 'Describe what logs you want to find...',
+      },
     },
     {
       id: 'logFrom',
@@ -374,6 +475,20 @@ Return ONLY the relative time string - no explanations, no quotes, no extra text
 ]`,
       condition: { field: 'operation', value: 'datadog_send_logs' },
       required: true,
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a JSON array of Datadog log entries based on the user's description.
+Each log object should have:
+- "message": The log message text
+- "service": The service name
+- "ddsource": The log source (e.g., "custom", "nodejs", "python")
+- "ddtags": Comma-separated tags (e.g., "env:production,version:1.0")
+- Optional: "hostname", "status" (info/warn/error)
+
+Return ONLY valid JSON - no explanations, no markdown code blocks.`,
+        placeholder: 'Describe the logs you want to send...',
+        generationType: 'json-object',
+      },
     },
 
     // ========================
@@ -393,6 +508,15 @@ Return ONLY the relative time string - no explanations, no quotes, no extra text
       type: 'long-input',
       placeholder: 'Scheduled maintenance',
       condition: { field: 'operation', value: 'datadog_create_downtime' },
+      wandConfig: {
+        enabled: true,
+        prompt: `Generate a downtime message for Datadog based on the user's description.
+The message should explain why monitoring is being muted.
+Examples: "Scheduled maintenance window", "Deploying new version", "Infrastructure upgrade in progress"
+
+Return the message text directly - no extra formatting.`,
+        placeholder: 'Describe the reason for the downtime...',
+      },
     },
     {
       id: 'downtimeStart',