SiftHub connects to Weflow and brings your call transcripts into SiftHub as searchable knowledge. Your team can find what was said on customer calls and cite it in Answers, Autofill, Proposals and Pulse, without leaving SiftHub.
What Gets Connected
SiftHub connects to one Weflow workspace. You choose which calls SiftHub indexes, and you can combine any of these options:
| Option | What’s connected |
|---|---|
| All calls | Every external call in the lookback window (6 months by default) |
| Calls by user | External calls in the lookback window where an email address you provide is a host or participant |
| Specific calls by URL | Only the calls whose links you provide. These are included even if they’re internal-only or older than the lookback window |
For Specific calls by URL, send the link from your browser’s address bar while the call is open in Weflow. Don’t send the share-recording link.
Note: SiftHub connects only external Weflow calls by default. Calls you select by URL are the only exception.
Supported Content
| Content | Support | Details |
|---|---|---|
| Call transcript | ✅ Yes | The transcript Weflow generated for the recording |
| Weflow AI summary | ✅ Yes | Weflow’s default summary template. When a summary is available, it’s also shown in SiftHub search results |
| Call metadata | ✅ Yes | Title, start time, duration and language |
| Participants | ✅ Yes | Names, emails and roles. Used for the Calls by user option and Host and participant access |
| Linked Salesforce records | ✅ Yes | Each call stays linked to its Salesforce record in SiftHub |
| Internal-only calls | ❌ No | Unless you select them by URL |
| Call video and clips | ❌ No | SiftHub indexes the transcript, not the recording. To watch a call, open it in Weflow |
| Comments, interaction metrics, scorecards and trackers | ❌ No | Weflow’s call analytics and team annotations stay in Weflow. Only the transcript, AI summary and call details are brought into SiftHub |
Access Control
You choose one of these access options with your CSM:
| Option | Who can see connected calls |
|---|---|
| All | Every SiftHub user in your organization |
| Host and participant | Only users who were a host or participant on the call |
Important: Weflow’s API doesn’t share whether a call is marked private. A call marked private in Weflow can still appear in SiftHub for anyone who has access under the option you choose.
Using Weflow Content in SiftHub
After the first sync finishes, connected calls appear wherever SiftHub uses company knowledge:
- Search and Answer: Transcripts appear in search results and can be cited as sources in AI-generated answers.
- Proposals and Autofill: Weflow calls can back up generated answers in proposals and questionnaires.
- Pulse: Connected calls feed Pulse in the same way as other call recording connectors.
- Collections: Add all connected Weflow calls to a Collection.
Clicking a Weflow source opens your Weflow recordings page (app.getweflow.app/ci/recordings) in a new tab. If the call can’t be opened, see Troubleshooting.
Weflow Content in Collections
When Weflow is connected, each Collection has a Weflow tab. In this release, you can link or delink all connected Weflow calls at once.
To link all calls:
- Open the Collection and go to the Weflow tab.
- Turn on the Link all toggle.
- In the Link all items? window, click Link all.
To delink all calls:
- Turn off the Link all toggle.
- In the Delink all items? window, confirm. All connected Weflow call transcripts are removed from the Collection.
Note: Linking specific calls from the Collection is coming soon. In the meantime, your CSM can link specific calls for you.
Content Updates
SiftHub checks Weflow for new and updated calls every 30 minutes.
If a call doesn’t have a transcript yet, SiftHub keeps checking. If a transcript never arrives, the call isn’t indexed. If a call is deleted from Weflow, it’s removed from SiftHub search, Collections and Pulse context.
Weflow Connector Setup
Setup is done by a Weflow admin working with your SiftHub Customer Success Manager (CSM). You generate an API key in Weflow, decide what to connect, and share both with your CSM, who activates the connector.
Before you begin
- Weflow admin access: A Weflow admin needs to enable API access and generate the key.
- A Weflow plan with API access: If you’re not sure your plan includes it, ask your Weflow customer success contact or Weflow support. Without API access, SiftHub can’t connect, and the Weflow card shows an error after a connection is attempted.
Step 1: Generate an API key in Weflow
- Sign in to Weflow as an admin and open the Admin Console.
- Generate an API key for the workspace you want to connect. The key starts with
wfl_. - Copy the key and store it securely. Treat it like a password: it gives access to call data in that workspace.
For more details, see Weflow’s Public API Overview.
Note: SiftHub only reads from Weflow. It never creates, edits or deletes anything in your Weflow workspace, and it doesn’t request video downloads or streaming links.
Step 2: Choose what to connect
Using the options in What Gets Connected and Access Control, decide:
| Setting | What to decide |
|---|---|
| Sync scope | All calls, Calls by user (with the email addresses), Specific calls by URL (with the call links), or a combination |
| Access | All, or Host and participant |
| Lookback window | 6 months by default. Applies to All calls and Calls by user; calls selected by URL aren’t limited by it |
Step 3: Share the details with your CSM
Send these to your CSM through your agreed secure channel:
- The Weflow API key
- Your sync scope, including any email addresses or call links
- Your access option
- Your lookback window, if it’s different from the 6-month default
Optional: Request a connection from SiftHub
While you’re working with your CSM, an admin can also send a request from SiftHub:
- Go to Connectors > Admin apps.
- Find the Weflow card (Connect call transcripts and insights from Weflow). Expand it to see what will be connected, or click Connect.
- In the Connect Weflow window, add a message if you like, then click Send request. Your CSM will be in touch shortly.
Note: Sending a request doesn’t connect Weflow by itself. Your CSM still needs the API key and the settings from Step 2.
Activate the Weflow Connector
Your CSM activates the connector using the details you share. There’s no API key field, scope picker or disconnect option in SiftHub in this release. To change what’s connected, or to disconnect, contact your CSM.
While the first sync runs, the Weflow card shows Connected and Sync in progress. When the sync finishes, it shows Connected and the Last sync time.
Time to Activation
The connector is usually activated within 48 business hours after your CSM receives the API key. Your CSM will confirm once it’s active and the first sync has finished. Connected calls are searchable as soon as that first sync completes.
Troubleshooting
| What you see | What to do |
|---|---|
| The card stays on Sync in progress for a long time | Weflow may be limiting how fast SiftHub can fetch calls. SiftHub keeps retrying in the background, and no error is shown. If the sync doesn’t finish, contact your CSM. |
| A recent Weflow call isn’t in SiftHub yet | SiftHub checks for new calls every 30 minutes. Calls without a transcript yet are retried, and aren’t indexed if a transcript never arrives. |
Need Help?
Contact your SiftHub Customer Success Manager.