---
name: finta-install-auth
description: 'Set up Finta fundraising CRM account and configure integrations.

  Use when onboarding to Finta, connecting email/calendar,

  or configuring investor pipeline automation.

  Trigger with phrases like "install finta", "setup finta",

  "finta onboarding", "configure finta crm".'
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.7.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - fundraising-crm
  - investor-management
  - finta
compatibility: Designed for Claude Code
title: finta-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/finta-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/finta-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/finta-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/finta-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/finta-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/finta-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/finta-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Finta Install & Auth

## Output

Record only the authentication method, workspace owner, granted scope, validation timestamp, and secret-manager reference. Never paste credentials, authorization headers, or user information into tickets or logs.

## Examples

Authorize a staging integration using a least-privilege credential stored by the deployment platform. Perform a read-only validation with a synthetic workspace, then verify that revoking the credential stops access before any production use.

## Overview

Set up Finta fundraising CRM at trustfinta.com. Finta is a UI-first platform for managing fundraising pipelines, investor relationships, and deal rooms. Integration is via email/calendar sync and the Finta web app -- there is no public REST API.

## Prerequisites

- Finta account at https://www.trustfinta.com
- Gmail or Outlook email for sync
- Google Calendar or Outlook Calendar

## Instructions

### Step 1: Create Account

1. Sign up at https://www.trustfinta.com
2. Complete onboarding wizard with company details
3. Select your fundraising stage (Pre-seed, Seed, Series A, etc.)

### Step 2: Connect Email

Finta syncs with Gmail and Outlook to automatically track investor communications:

1. Go to **Settings** > **Integrations**
2. Click **Connect Gmail** or **Connect Outlook**
3. Grant read access for email tracking
4. Finta will auto-detect investor conversations and update pipeline stages

### Step 3: Connect Calendar

1. Go to **Settings** > **Integrations**
2. Click **Connect Google Calendar** or **Connect Outlook Calendar**
3. Meetings with investors will auto-log to the pipeline

### Step 4: Import Existing Investors

- **CSV Import**: Upload a spreadsheet with investor name, firm, email, stage
- **Manual Entry**: Add investors one by one in the Pipeline view
- **Aurora AI**: Let Finta's AI prospect matching find relevant investors

### Step 5: Configure Pipeline Stages

Default stages (customizable):

1. Researching
2. Reaching Out
3. Intro Meeting
4. Follow-up
5. Due Diligence
6. Term Sheet
7. Closed

## Error Handling

| Issue | Cause | Solution |
|-------|-------|----------|
| Email sync not working | OAuth expired | Reconnect in Settings > Integrations |
| Calendar events missing | Wrong calendar selected | Select correct calendar |
| CSV import fails | Wrong format | Use Finta template CSV |
| Duplicate investors | Re-import | Merge duplicates in UI |

## Resources

- [Finta Website](https://www.trustfinta.com)
- [Finta Blog](https://www.trustfinta.com/blog)
- [Finta for Serial Entrepreneurs](https://www.trustfinta.com/blog/finta-for-serial-entrepreneurs-fundraising)

## Next Steps

Proceed to `finta-hello-world` to set up your first fundraise pipeline.
