Connect CallRail to PostgreSQL

Start with a connected CallRail source and an existing PostgreSQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "numbers" table.

Select concrete CallRail fields such as Total Call Abandoned, Calls AVG Duration, Call Answer rate, and Day of the month. You can rename the chosen columns, preview the result, and write them to PostgreSQL tables such as accounts, companies, and numbers.

Set an initial fetch period for CallRail, then choose the frequency and lookback window for the job writing to "numbers". Catchr rewrites that selected period on each run.

The partition field tells Catchr which CallRail rows in "numbers" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.

With CallRail data, a PostgreSQL query can summarize calls, answered calls, duration, and answer rate by acquisition source. A query built around Total Call Abandoned and Calls AVG Duration can support trend reviews, account comparisons, and operational reporting.

Yes. Connect an existing PostgreSQL database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.