Product Guide · Knowledge and Strategy
Synced sources
Synced sources keep material that changes elsewhere in your knowledge base without uploading it again: Markdown files from a GitHub repository, files you pick in Google Drive, your Granola meeting notes, and each profile's own published LinkedIn posts. Scripe re-reads them on its own, and every run says what it added, updated, removed and skipped.
It is for admins who connect a workspace's tools, and for solo creators who keep their notes in one of them. Anyone in the workspace can use what a source syncs; connecting and managing GitHub, Google Drive and Granola needs the Admin role.
How it works
Each source gets its own folder in the knowledge base. A source connected from the knowledge base's main list is visible to the whole workspace; one connected from inside a profile's folder belongs to that profile. That choice is made when you connect and stays with the source.
Scripe re-reads sources in a nightly pass. Sync now in the source's settings starts a run at once. A Granola workspace that supports it also tells Scripe about new and edited meetings as they happen.
Every run ends with a summary: Added, Updated, Removed, Unchanged, Skipped and Failed, with the files named. The source's status reads Everything synced only when the last run finished everything; Partly synced and Sync failed say otherwise.
Open a source from the Synced status on its folder, or from Sources in the knowledge base toolbar.
The sources
| Source | What syncs | How to connect |
|---|---|---|
| GitHub repository | Markdown and text files (.md, .mdx, .markdown, .txt) of one repository, from its default branch or a branch you name, optionally from one folder | Install the Scripe app on the GitHub account that owns the repository, then choose the repository |
| Google Drive | The files you pick: Google Docs, Sheets and Slides, and Markdown, text and CSV files | Connect Google Drive, then Choose files. Scripe only ever gets access to the files you pick. |
| Granola | Each meeting's AI summary; transcripts only if you turn them on | Paste a Granola API key, optionally choose folders |
| Post history | The profile's own published LinkedIn posts, one document each | Nothing to connect: it appears in each profile's folder |
Google Drive syncs individual files, not folders.
Granola
- The key: Granola issues API keys on its Business and Enterprise plans, under Settings → Connectors → Workspace API keys. A workspace key keeps working when people leave; a personal key reads only the notes its owner can see and stops when their account or key does. Scripe can read only what the key can read.
- Folders: choose up to 20 Granola folders or spaces, including everything inside them, or leave it empty to sync every meeting the key can read.
- Transcripts are off by default. Scripe syncs each meeting's AI summary, which is what content generation reads. Turning on Also sync full transcripts stores every word said in the meeting, by everyone in it, including people who are not Scripe users. Changing the setting rewrites every meeting on the next sync.
Post history
Every personal profile that finished its setup, and every Company Page, gets a Post history folder in its profile folder when you open the knowledge base. It cannot be disconnected; it would come back on your next visit. It needs no plan.
How deletion works, per source
Each source decides what a missing item means differently, on purpose:
- GitHub: a file deleted from the repository, or moved out of the folder you sync, is removed from the knowledge base on the next run.
- Google Drive: removing a file from your picked files deletes its document. A file deleted or moved to the trash in Drive is removed on the next run. A file Scripe can no longer read, for example because sharing changed, is kept and marked as no longer updating.
- Granola: a meeting that disappears from Granola's answer is never deleted. Granola leaves meetings out for reasons that are not deletion, so Scripe keeps the meeting and marks it as no longer reachable. A meeting is removed only when Granola confirms it moved out of the folders you sync. If a run returns less than half the meetings of the last complete run, Scripe stops and changes nothing until you confirm with This is expected — sync again.
- Post history: removing a post is an exclusion, not a delete. See Removing a post.
Disconnect on GitHub, Google Drive or Granola deletes the documents that source created and withdraws Scripe's access. Your files and notes at the source are not touched, and what you added another way stays.
Removing a post
Select posts in a profile's Post history folder and press Remove from knowledge base. The post stays published on LinkedIn and in the post history. Scripe stops using it as knowledge, as a writing sample and as an example of past results, and ideas and drafts for the profile no longer draw on it.
Restore a post from Removed posts in the folder's settings. Anyone who works on the profile can remove or restore posts; no special role is needed.
Limits and plans
| What | Limit |
|---|---|
| GitHub, Google Drive, Granola | Solo, Advanced and Business. See Plans. |
| Post history | Every plan |
| Files per source | 2,000 |
| Size per source | 50 MB in total |
| Size per file | 2 MB of text |
| Granola folders | 20 |
When a source reaches a limit, nothing is deleted: the documents already synced stay, and files past the limit are skipped and named. If the workspace's plan no longer includes synced sources, they pause and start again on their own once it does; nothing is deleted.
Edge cases
- The person who connected Granola deletes their Scripe account: the source, its folder and its meetings stay; only the key is removed. Reconnect with a new key to resume syncing.
- A source needs reconnecting: Scripe lost access, for example because a grant was revoked. It stops syncing until you reconnect; documents already in the knowledge base stay where they are.
- A profile without a LinkedIn connection: its post history keeps the posts it holds and does not update.