Help Needed: Setting Up Scheduled Runs for Clay and Apify

We've recently introduced Clay Scheduling, which allows you to set up automated runs for both sources and columns. Here's how you can set it up: 1. For scheduled sources: • This keeps your data current by automatically refreshing on a daily, weekly, or monthly basis. 2. For scheduled columns: • While in a table, click the ⛭ icon on the top right. • Under 'Run the table', select 'On a schedule'. • Choose the frequency: daily, weekly, or monthly. • Decide to run all columns or only selected ones. For Apify integration: ** Connect your Apify account in Clay settings or when running an Apify integration. ** Use the Apify integration to retrieve data or launch actors directly in Clay. If you need more assistance, please request human help by clicking on 'Talk to a person'.

Sources: Build a sustainable growth engine with Scheduling - The GTM with Clay Blog Scheduled columns | Documentation | Clay University Scheduled columns | Documentation | Clay University Apify integration | Documentation | Clay University

Hi Annamarie, thanks for your message. Apify integrates with Clay, so you'll be able to build tables based on Apify actor runs, or trigger actor runs at strategic points in your workflow. Here's how you can set up a Clay table from an Apify actor run:

And here's how you can trigger an Apify actor in an active workflow:

For the trigger-based approach you'll likely have to study the documentation of the specific actor, to see what JSON payload it expects to trigger the run.

Hi Annamarie - happy to help here! Can you clarify where we could assist here? Happy to fill in any context that's missing on our end.

Annamarie - Do you mind sending the link (url) to the table so we can take a look?

Is this the actor which you're showing in the loom video?

It looks like you were able to import the run results in your table source - are there any other issues you're running into here?

As for the deduplication aspect on Apify's side, this is not something we have control over, but rather something that pertains to the logic of the actor itself. What clay can do is import net new records on a schedule. Here's some context on how you can set this up: https://www.loom.com/share/a4f11ab84ba24f3a879221a1f5bdbc2d?sid=a210b47e-8322-4df0-8bbf-aaf1618e8b7e I hope this was helpful. If there's anything else I can assist you with, please let me know!

I'm not sure what you're referencing here with the "created at button" - any context would be helpful here!

Here's a quick video to explain: https://www.loom.com/share/445672020d0e4a0d9d5e21e59aa55060?sid=1b343282-a98f-4d72-b8ce-366b3f2cef56 Let me know if this makes sense!