--- title: "Connect Nooks to Rig — Rig guide" description: "Connect Nooks to Rig through your own S3 bucket. Syncs one row per dialer call with participants, disposition and the full transcript into your warehouse." canonical: "https://rig.so/guides/connect-nooks" format: markdown --- Search guides, references, playbooks…⌘K Browse guides # Connect Nooks to Rig Sync your Nooks dialer calls into Rig through an S3 bucket you own. Nooks has no export API, so it drops one ZIP per call into your bucket and Rig reads the new ones each sync. ## Before you start - Nooks must already be exporting call data into an S3 bucket in your AWS account. Nooks lists the transcript export as an admin feature, so ask your Nooks admin or Nooks support to set it up. - You need an AWS access key that can list the bucket and read the files in it. - Know your company email domain. Rig uses it to tell your reps from the prospects on each call. ## Step 1: Point Nooks at your S3 bucket Nooks publishes no step-by-step guide for this, so the exact screens are not listed here. 1. Create or choose an S3 bucket in your AWS account. 2. Ask a Nooks admin, or Nooks support, to export call data into that bucket. See Nooks' release note on transcript data export. 3. Check that ZIP files named like `Nooks--.zip` start to appear, in a folder for each day. 4. Create an AWS access key with read-only access to the bucket. Copy the access key ID and the secret access key. ## Step 2: Connect it in Rig New to Rig? Watch how to find Connections Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source. 1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`. 2. Search for **Nooks (S3 call exports)**, open the card and click `Connect`. 3. **Export bucket URL**: the bucket Nooks exports into, in the form `s3://your-bucket-name/`. 4. **Company email domain**: your own domain, such as `example.com`. People on this domain count as the rep side of a call and everyone else as a prospect. 5. **File glob pattern**: pre-filled with `**/Nooks-*.zip`. Leave it as it is. 6. **AWS access key ID (optional; instance role used if blank)**: paste the access key ID for the read-only key. 7. **AWS secret access key (optional)**: paste the matching secret access key. 8. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`. 9. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection. ## What Rig pulls in Nooks lands in its own `nooks` schema in your warehouse: - **Calls**: one row per call with participants, direction, disposition, start and end time and the full transcript. ## Good to know - Each ZIP holds a metadata file and a transcript file. Nooks writes them once and never changes them, so Rig opens each archive a single time. - If a call has no participant on your email domain, Rig falls back to the `(User)` tag in the transcript to find the rep. - Recordings are not synced. Only the call metadata and the text transcript are. - To disconnect Nooks, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse. ## What people use this for - Measure outbound call outcomes by disposition - Search call transcripts for what prospects say - Compare rep activity and talk patterns [More ideas for using Nooks](https://rig.so/integrations/nooks) ## Nooks documentation - [Nooks release note: transcript data export](https://www.nooks.ai/blog-posts/november-product-release-do-not-call-report-transcript-data-export-ai-call-insights-navigation) Was this guide helpful? Yes No --- - [This page as HTML](https://rig.so/guides/connect-nooks) - [Site map for language models](https://rig.so/llms.txt) - [API and agent documentation](https://rig.so/developers)