{{rail.flashText}}

Connections

Connect your tools, turn what arrives into records, and connect Claude

Events this week3,180From {{srcCount}} sources
Kept as signals31010% · the rest was noise or repeated
To pods directly262About existing customers
To Radar48New companies to qualify

Connected{{srcCount}}
{{r.events}} events · {{r.kept}} kept {{r.status}}

Where signals go

PAbout an existing customerStraight to the pod that owns it
RAbout a new companyTo Radar, if the lead score is {{minScore}} or more
–Low confidence or repeatedDropped, kept 30 days for review

Existing data

Bring customers, contacts and history from a CRM or a spreadsheet on day one. Each customer lands in the pod you choose.
Runs today{{runsToday}}Across {{jobCount}} jobs
Records created286Activities, signals and Radar leads
Needs a look{{failedCount}}Failed runs to reprocess
Median time4 secondsFrom event to record

Jobs{{jobCount}}

{{job.name}}

{{f.label}}→
Test passed{{job.testText}}

When this happens

{{job.where}}{{job.whereNote}}

Do this with the model

Use the shared signal rules
Uses the instructions, types and thresholds in Signal rules.

Then create

{{m.from}} → {{m.to}} {{m.rule}}

Recent runs{{job.runCount}}

{{r.state}} {{r.input}}{{r.result}} {{r.when}}

Bring data in

{{t.n}}{{t.label}}
What is it
Drop files here, or choose filesCSV, Excel or JSON · up to 20 files at once · customers.csv and contacts.xlsx chosen
Your model matched the columns. Check them, then import. 421 rows in 2 files.
{{m.from}}→{{m.to}}{{m.conf}}
{{ioDone}}Rows imported
{{ioFailed}}Rows failed
BackgroundYou can leave this page
Row {{e.row}}{{e.what}}{{e.fix}}
Every row is inThe failed rows were fixed and imported. Customers landed in the pods you chose.

Take data out

Data
Format
When

Background jobs{{bgCount}}

{{b.name}}{{b.sub}}{{b.state}}

Model

The model you bind reads every event
Provider
KeyStored in vault

Instructions

How to vet an event and turn it into a signal
{{promptNote}}

Test with a real event

{{verdict}}
{{testOut}}

Signal types{{typeCount}}

Output fields{{fieldCount}}

Click to make required

Thresholds

Applies to new events

Alerts{{alertCount}}

{{a.name}}To {{a.who}}

Rules for everyone

P1 issues and overdue first contacts ignore quiet hours. When someone is away, their alerts go to their backup on the customer.

Claude tools{{toolCount}} in {{groupCount}} groups

{{g.n}} {{g.who}}
{{t.name}} {{t.desc}} {{t.kind}}

Server

Add to Claude as a custom connector
https://neupods.com/mcp
People sign in with their neupods account. Claude gets the same role and pods they have in the app.
Claude shows what it will change and waits for a yes

Recent actions from Claude

{{r.tool}}{{r.who}} · {{r.what}}{{r.when}}

Send data in

https://api.neupods.com/v1
{{r.method}}{{r.path}}{{r.desc}}

Send events out

API keys{{keyCount}}

{{k.name}}{{k.scope}} · {{k.used}}{{k.tail}}

A signed customer from outside

If an agency or another team wins a customer on its own, they send it to /v1/customers with the pod code. It arrives in that pod tagged with its source, and counts in the pipeline as won.