CONNECT APP
Build with Logfire
Artificial Intelligence (AI)
- API key
MCP
Give your agent Logfire tools
Every Logfire action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Logfire account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "logfire",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Record Log Entry:
const result = await mcp.callTool({
name: "logfire-record-log-entry",
arguments: {
message: "Message",
level: "Level",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "logfire",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Record Log Entry:
result = await session.call_tool("logfire-record-log-entry", {
"message": "Message",
"level": "Level",
})API PROXY
Call the Logfire API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Logfire API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Logfire endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Logfire actions from your backend
Connect a user's Logfire account once, then run Record Log Entry on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "logfire-record-log-entry",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
logfire: { authProvisionId: "apn_xxxxxxx" },
message: "Message",
level: "Level",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="logfire-record-log-entry",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"logfire": {"authProvisionId": "apn_xxxxxxx"},
"message": "Message",
"level": "Level",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "logfire-record-log-entry",
"configured_props": {
"logfire": { "authProvisionId": "apn_xxxxxxx" },
"message": "Message",
"level": "Level"
}
}'TOOLS
Logfire actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Record Log Entry
actionRecords a single log entry or event in Logfire as a zero-duration span, via OTLP ingestion. Use this whenever the user wants to log, record, or note an event, deployment, incident, or error — this is Logfire's equivalent of callinglogfire.info()/logfire.error()from the SDK. This creates a single point-in-time entry, not a full distributed trace with parent/child spans. SettingexceptionType/exceptionMessagemarks the entry as an exception (is_exception = truewhen later queried). After recording, use Run SQL Query to confirm what was written (e.g.SELECT * FROM records WHERE message LIKE '%...%' ORDER BY start_timestamp DESC LIMIT 1). See the documentationWritev0.0.2 -
Run SQL Query
actionExecutes an arbitrary SQL query against Logfire'srecords(unified logs + traces, one row per span) ormetricstables and returns the results. Use this for any analysis, search, or aggregation over your telemetry — recent activity, error hunting, latency analysis, counts, etc. To discover what columns are available before writing a query, runSELECT column_name, data_type FROM information_schema.columns WHERE table_name = 'records'(or'metrics') with this same tool — there is no separate schema-discovery tool. Useful columns onrecordsincludestart_timestamp,span_name,message,level,service_name,duration,is_exception,exception_type, andexception_message. Example — find exceptions:SELECT span_name, exception_type, exception_message FROM records WHERE is_exception = true ORDER BY start_timestamp DESC. Example — count by level:SELECT level, count(*) AS n FROM records GROUP BY level ORDER BY n DESC. After using Record Log Entry to write data, use this tool to confirm what was recorded. See the SQL reference and query API docs.Read-onlyv0.0.2
EVENTS
Logfire triggers
Event sources your backend can deploy for users and receive through a webhook.
No Logfire triggers are available yet.
- App slug
- logfire
- Authentication
- API key
- Categories
- Artificial Intelligence (AI)
- Actions
- 2
- Triggers
- 0
- API proxy
- Available