Template - Integrations
Connect [integration] to Riff to [what it does]. Riff handles the OAuth, stores tokens securely, and wires [integration] into your apps, automations, and agents.
What you can build (fast)
[what you can build] : e.g., [example of what it does].
x 3 examples
For example:
Daily/weekly summaries: send pipeline, support, or ops roll-ups into a channel at scheduled times.
Try these starters (“Riff this App”):
Create 3 app starter prompts using the example app title and prompt. Adjust based on the specific integration the examples below are only for HubSpot.
Dashboard
Campaign Attribution Dashboard
Build a dashboard that uses HubSpot contacts, deals and UTMs to show campaign-to-revenue attribution (CPA, ROAS, funnel conversion).
Automation
Contact hygiene
An app to find and merge duplicate HubSpot contacts by email/domain, flag missing key fields, and export a cleaned CSV for review.
AI Agent
Follow-up Email
An agent that reads the last HubSpot activity on a deal, drafts a tailored follow-up email with next steps, and logs the draft as a note. Trigger on button from the deal view.
Dashboard example
Build a dashboard that
Automation example
An automation that
Agent example
An agent that
3 x riff this app urlshttps://useriff.ai/home?prompt-template={prompt} format example:
Prerequisites
[integration] workspace where you can [prerequisite needed]
A Riff workspace (sign-in at useriff.ai).
Connect [integration] to Riff (two easy ways)
Let the agent drive When a task needs [integration], the agent prompts you to connect. Click the link, approve scopes once, done. The agent then tests the connection (“quick test”) and uses it in your build plan automatically.
Add proactively In your workspace, go + More → Integrations → [integration], authorise, and you’re ready. Riff manages tokens, scopes, and basic checks for you.
Tip: If an OAuth popup is blocked in the embedded preview, open your app in a new browser tab and retry the connect step.
Permissions (scopes) Riff requests in [integration]
Riff asks for tightly-scoped access. Here’s the high-level view of what the [integration] can view and do once installed:
Riff uses OAuth; tokens are stored securely and handled by the Integrations system (no hard-coding secrets in code).
How Riff wires [integration] for you (under the hood)
Sets up OAuth and stores tokens securely in Secrets/Integrations.
Adds minimal scopes, verifies them, and runs a simple test action.
Exposes [integration] as a usable service inside your tasks, automations, and agents (no manual boilerplate).
Security notes
Tokens are managed by Riff’s Integrations system; you don’t paste keys into code.
Frontend code never sees secrets; all actions run server-side.
Keep scopes tight; Riff requests only what’s needed for your flows and validates them.
Related docs & features
Last updated
Was this helpful?