Automations

What automations can do

Anything you can ask in a chat, you can run as an automation: a weekly scan for new candidates, a daily summary of your pipeline, a monthly market report.

Each run is a new chat in which SourceGeek works on the automation’s prompt, exactly as if you’d sent it.

Create an automation

1. Click Automations in the left rail, then + New automation
2. Give it a Name and, optionally, a Description
3. Write the Prompt: what SourceGeek should do each time
4. Choose a schedule:
   • Every N hours
   • Daily at a time
   • Weekly on a day and time
   • No schedule: it runs only when you click Run now or when its webhook is called
5. Check the Timezone
6. Choose whether to Share with workspace, and save

You can also ask SourceGeek in a chat, for example “every Monday at 8:00, find new data engineers in Amsterdam and add them to my sheet”. It asks you to approve before it creates the automation.

How runs work

• Scheduled runs start within about 5 minutes of their time. A new or changed schedule starts at its next occurrence
• Each run creates a personal chat for the automation’s creator, named after the automation. Open it from Runs to see what SourceGeek did and what it made
• SourceGeek can’t ask questions during a run. A run that needs an answer fails
• Actions in your connected tools, such as sending an email, don’t ask for approval in scheduled runs or Run now. Runs started by a webhook do. See Questions and approvals

The automation page

Click an automation to open it:

• Run now: start a run straight away
• Prompt: click to edit
• Schedule: change it and click Save schedule. The next run time is shown
• Runs: the 50 most recent runs, with when they started, how (scheduled, manual or webhook), how long they took and whether they completed or failed
• Enabled: switch off to pause the schedule and webhook. Run now still works

Trigger from another tool

Every automation has a Webhook URL, visible to its creator and workspace admins. Another tool, such as n8n or Zapier, can start a run by sending a POST request to it, optionally with a JSON body (up to 256 KB) that SourceGeek gets as extra information for the run.

Click Copy URL to copy it. Regenerate token makes a new URL and stops the old one.

Sharing

A personal automation is visible only to you. Switch on Share with workspace to let every member see and edit it. Only its creator can change this. Runs are always the creator’s chats.

Archive and delete

In the automation’s settings:

• Archive automation: stops and disables it, and moves it to the archived list (Automations panel filter → Archived). Restoring it doesn’t switch it back on: turn on Enabled yourself
• Delete automation: removes it and its run history for good

Credits

Each run uses credits like a chat: 1 credit for each answer plus what SourceGeek does along the way. An automation that runs often can use a lot of credits, so test the prompt in a chat first. Track usage under Credits and usage.

Without an active plan or trial, automations are paused: nothing runs and new ones can’t be created until an admin chooses a plan.