SiftHub's Octave Connector integrates your Octave GTM Library directly into SiftHub. The personas, offerings, competitive positioning and proof points your team maintains in Octave become searchable knowledge, available when answering RFPs, security questionnaires and buyer questions.
What Gets Connected
SiftHub connects to one Octave workspace. For each Library entity type you choose whether to connect all of its records, only specific records, or none. That way you can bring across what your team answers questions from and leave the rest.
| Entity type | What it holds |
|---|---|
| Products | What you sell, including summary, capabilities, differentiated value and the problems it addresses |
| Services | Services you deliver, with deliverables, competencies and customer benefits |
| Solutions | Packaged combinations of products and services, and the capabilities they add together |
| Core Features | Individual capabilities belonging to one offering: what each does, how it works and why it exists |
| Personas | Buyer roles, with job titles, responsibilities, pain points, concerns and objectives |
| Segments | Target markets, with firmographics, buying dynamics, market pressures and strategic priorities |
| Use Cases | The jobs buyers hire you for, with scenarios, business drivers and desired outcomes |
| Competitors | Named competitors and how your team positions against them |
| Alternatives | Options other than a vendor, including building in house or doing nothing |
| Objections | Objections your team hears, with the approved responses |
| Buying Triggers | Events that signal a buyer is in market |
| Proof Points | Evidence that supports a claim, such as certifications, metrics and outcomes |
| Reference Customers | Customers you can reference, with the detail that makes them usable in a response |
Note: SiftHub connects to one Octave workspace. Connecting more than one Octave workspace is not supported. If your organisation runs several, choose the one that holds the Library your team answers questions from.
Supported Content
For every connected entity type, SiftHub indexes:
- The record's authored content. Every field your team has filled in, such as a persona's pain points or a proof point's supporting evidence.
- Custom fields. Any additional fields your workspace has defined on an entity type.
- Relationships between records. Which personas, segments, competitors and proof points belong to which offering.
Not connected
The following are not indexed by this connector:
- Motions and Motion Playbooks
- Skills
- Resources and Assets, including hosted files
- Analytics, insights and scheduled reports
- Call transcripts and conversation data
Note: Call transcript content is served by separate SiftHub connectors. If your team relies on it, speak to your CSM about connecting that source as well.
Access Control
Octave does not provide permissions on individual records, so there are none for SiftHub to carry over. All content from the connected entity types is available to every active SiftHub user who has access to this source. Different users will not see different Octave results.
Using Octave Content in SiftHub
Once connected, Octave records are available wherever SiftHub uses company knowledge:
- Search. Records appear in results alongside your other connected sources.
- AI answers. Records are used as sources, with attribution.
- AI Teammate. When a record is relevant, the records linked to it in Octave are brought in alongside it, so an answer about an offering arrives with its personas, proof points and objections rather than on its own.
- Pulse. Nudges are refined using the strategy held in your Library, so what Pulse surfaces reflects the segments, personas and positioning your team has defined in Octave.
Each record appears as its own result, labelled with its entity type, so it is clear whether an answer is drawing on a persona, a proof point or a competitor. Results link back to the record in Octave.
Note: Because relationships come from Octave, the quality of what SiftHub brings in alongside a record depends on how your team has linked records in the Library. Records with no links are still indexed and still searchable on their own.
Content Updates
Changes in Octave are reflected in SiftHub within 30 minutes. This covers:
- New records in any entity type set to All
- Edits to existing connected records, including custom fields
- Records deleted or archived in Octave, which are removed from SiftHub results
- Changes to how connected records are linked to one another
Note: New records are picked up automatically only for entity types set to All. Where a type is set to Specific, the connection covers the records you named. Anything added in Octave afterwards needs to be sent to your CSM before it appears in SiftHub.
Octave Connector Setup
Setup is usually completed by an Octave workspace admin working with your SiftHub CSM. There are three steps on your side:
- Generate an API key in your Octave workspace
- Decide which entity types to connect
- Share the key and your selection with your CSM
Before you begin
- Octave admin access. You need access to the Octave workspace you want to connect, with permission to create API keys.
- The right workspace. Octave issues a key for each workspace, so identify which one holds the Library your team answers from.
Step 1. Generate an API key in Octave
1. Open your Octave dashboard. Sign in at app.octavehq.com and switch to the workspace you want to connect.
2. Create an API key. Create and manage API keys from the dashboard. Each key works for one workspace only, so confirm you are in the correct workspace before creating one.
3. Note your workspace ID. Your workspace ID appears in the Octave address bar, in the form app.octavehq.com/o/your-org/wa_xxxxxxxxxxxx/…. The part beginning wa_ is the workspace ID. Copy it alongside the key.
4. Confirm your Octave address. For most workspaces this is https://app.octavehq.com. If Octave has given your organisation a different address, use that instead.
SiftHub only reads from Octave. It never creates, edits or deletes anything in your Library.
Step 2. Choose which entity types to connect
Using the table in What Gets Connected, go through the entity types and decide what each one should contribute. There are three choices per type:
| Choice | What it means | What to note down |
|---|---|---|
| All | Every record of that type is connected, including records added later | The entity type name |
| Specific | Only the records you name are connected | The entity type name, plus the Octave page link or record ID for each record |
| None | That type is not connected | Nothing |
To identify a specific record, open it in Octave and copy the page link from your browser. The link contains the record's ID, so either the full link or the ID on its own is fine.
If you are not sure where to start, setting the types your team answers from to All is the usual approach. Choosing Specific is most useful where a type holds a lot of records but only some are approved for use with customers.
Note: A type set to All picks up new records automatically. A type set to Specific does not, so records added in Octave later need to be sent to your CSM to be included.
Step 3. Share the details with your CSM
Send the following through your agreed secure channel:
- The Octave API key
- Your workspace ID, beginning
wa_ - Your Octave address, usually
https://app.octavehq.com - Your choice of All, Specific or None for each entity type, with the page links or record IDs for anything marked Specific
Activate the Octave Connector
Your CSM activates the connector using the details you provide.
| What you provide | Why it is needed |
|---|---|
| Octave API key | Lets SiftHub read the Library |
Workspace ID (wa_…) | Identifies which Octave workspace to read |
| Octave address | Usually https://app.octavehq.com |
| Per-type selection | All, Specific or None for each entity type, with page links or record IDs for anything marked Specific |
Time to activation
Your CSM will confirm once the connector is active and the first sync has finished, typically within 24 hours of sharing the required workspace and entity details. Octave records become searchable as soon as that first sync completes.
Need help?
Contact your SiftHub CSM, or reach out to SiftHub support.