Channeled

Job change signals only detect actual job changes, not new records added to your monitoring table. Adding more records won't trigger updates unless those contacts have actually changed jobs. If your signal isn't processing correctly, try using the Force Run option in table settings, or delete and recreate the signal column with fresh mapping. Remember that signals monitor for real job changes over time, not table additions.

Source: Sources | Documentation | Clay University

The lookup single row enrichment can only filter using one column at a time, which may cause mismatches when you need multiple criteria. To improve matching accuracy: • Use a unique identifier - Email addresses work best as lookup values since they're typically unique • Check your filter settings - Ensure you're using "equal to" rather than "contains" for exact matches • Verify the lookup column - Make sure the column you're searching in actually contains the values you're looking for If you need to match on multiple criteria, consider creating a merged column that combines the values you want to match on, then use that as your lookup field.

Sources: Hide, Re-order, Sort, Filter, Merge Columns Google Sheets integration overview | Documentation | Clay University

Great! For extracting titles and authors from your medical reports data, use the "Extract Values from Data" integration: 1. Add "Extract Values from Data" column 2. Set your HTTP API response as the data source 3. Create separate extractions for titles and authors 4. Use dot notation like reports.title and reports.authors for nested data For flattening multiple reports per row, after extraction you can use the "write to table" feature to create separate rows for each report.

Source: Extract Values from Data with Clay

Use the Extract Values from Data integration to pull out titles and authors from your HTTP API response. For flattening multiple reports per row, use the splitting data feature: 1. Add the "Extract Values from Data" column 2. Set your data source as the HTTP API response column 3. Choose extraction type for titles and authors separately 4. Use formulas to split comma-delimited values into separate columns You can create separate columns for each extraction (titles, authors) and use dot notation for nested data paths like reports.title or reports.authors.

Source: Extract Values from Data with Clay

Clay doesn't have a direct integration with Outlook for email sending. However, we do have a native email sequencing beta feature that allows you to send emails directly from Clay without needing external tools. For Outlook integration specifically, you would need to use our HTTP API to connect to any email tool you want. We integrate natively with Smartlead, Instantly, Salesloft, Outreach, and HubSpot, but Outlook isn't among our direct integrations. Are you looking to send emails through your existing Outlook account, or would you be interested in exploring our native email sequencing feature instead?

Source: FAQ | Clay.com

Yes, we have a native email sequencing beta feature that allows you to send emails directly from Clay. However, Clay doesn't specifically integrate with Outlook for email sending. We integrate natively with Smartlead, Instantly, Salesloft, Outreach, HubSpot and others, or you can connect to any tool using HTTP API. For the native sequencing feature, you'll need a table with lead data including email addresses, and you can automate email campaigns within Clay.

Source: FAQ | Clay.com

The Get call details action allows you to select which details to pull from the call, but the documentation doesn't specify all available fields. You can configure what information to retrieve by selecting the "Details to pull" option when setting up the action. What specific details are you currently seeing available in the "Details to pull" dropdown when you configure the Get call details action?

Sources: Gong integration | Documentation | Clay University Gong integration | Documentation | Clay University

For enrichments not running since Aug 18th, try these solutions: Quick fixes: ** Click on the affected cell and select "re-run this cell" ** Toggle auto-update off and on again, then accept the run prompt For queued enrichments: ** Click the column header of the queued column ** Hover over "Run column" in the dropdown ** Select "Force" to jump start the run Check auto-update settings: ** Verify auto-update is enabled at table level (bottom-right corner) * Check column-level Run Settings at the bottom of enrichment columns These steps help recover from front or back-end performance issues and won't incur additional charges.

Absolutely, here's a guide on setting up Clay x Google sheets integration: Google Sheets x Clay