Connect Tempo to Perplexity
Send Tempo customers, accounts, worklogs and 1 more data type to Perplexity on a schedule. Refresh as often as every 15 minutes.
Perplexity
Who logged the most hours in Tempo last week, and on which projects?
Querying the Tempo data set in Coupler.io
How to connect Tempo and Perplexity
4 steps. You can preview the Tempo data in Coupler.io before anything reaches Perplexity.
Step 1 of 4
Connect Tempo
Enter your Tempo API token. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the Tempo data you want in Perplexity.
Step 3 of 4
Connect Perplexity
In Perplexity, add a connector named coupler-io that runs the Coupler.io MCP server in Docker, then paste your personal access token.
Step 4 of 4
Set a schedule
Perplexity sees the data as of the last run. Run it as often as every 15 minutes.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your Tempo integrations with these destinations
Get the most of Tempo to Perplexity integration
Gather data
Understand data
Automate data
Act on data
4 data types, including Customers, Accounts, Worklogs and Workload schemes.
With your Tempo API token, entered once when you add the connection.
No. The data stays in Coupler.io, and Perplexity queries it read-only when you ask a question. It can't edit or delete Tempo rows.
A Perplexity account and Docker. Perplexity reaches Coupler.io through a local MCP server that runs in Docker.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example Clockify or Harvest, and join or append them before the data reaches Perplexity.
