Skip to main content

Automate Redtail updates

Set Claude or ChatGPT to check FinMate for new meetings every couple of hours and save each meeting's notes and tasks to the matching contact in Redtail, with no clicking.

This works by giving your assistant two connectors: the FinMate connector to read your meetings, and the Orion connector to write to Redtail. Then a scheduled routine runs a prompt for you.

Before you start, read the data note on Connect FinMate to Claude or ChatGPT. Your meeting notes and client details are shared with your Claude or ChatGPT account.

Watch the 45-second walkthrough, or follow the steps below:

1. Connect the Orion connector​

Orion's Redtail CRM connector is available in Claude's connector directory.

  1. Open Claude and go to Customize > Connectors.
  2. Select Discover and search for Orion.
  3. Choose the Orion connector (by Orion) and click Connect.
  4. Sign in with your Orion / Redtail credentials when asked and approve access.

2. Connect the FinMate connector​

Follow Connect FinMate to Claude or ChatGPT if you haven't already.

Both connectors should now show as connected. Do a quick test in a normal chat first: ask "What was my most recent meeting in FinMate?" and "Find the contact Jane Smith in Redtail." If both work, you're ready.

When is a meeting ready for Redtail?​

A FinMate meeting moves through stages:

  1. Transcript. After the meeting, FinMate produces the transcript.
  2. Summary and tasks. These are only produced once a meeting type has been picked for the meeting.

Only a meeting that has reached stage 2 can be saved to Redtail, because that's where the notes and tasks come from. A meeting that has a transcript but no meeting type yet has nothing to save.

The routine below handles both cases. It saves the meetings that are ready, and it lists the recent meetings that are still waiting for a meeting type, so you can open them in FinMate, pick one, and let the next run pick them up.

3. Create the routine​

In Claude (or ChatGPT's scheduled-run feature, if your plan has one), create a new routine:

  1. Make sure the FinMate and Orion connectors are enabled for the routine.
  2. Paste the prompt below.
  3. Set the schedule to every 2 hours during business hours, for example weekdays from 8 AM to 6 PM in your time zone.

Prompt​

Look at my FinMate meetings from the last 7 days that have not been sent to my CRM yet.

For each one, work out how far along it is:
- Summary ready: reading the meeting's summary and action items from FinMate returns a summary.
- Transcript only: there is no summary yet ("not available for this meeting yet"), but the meeting has a transcript. To check, read just the first 30 seconds of the transcript (start 00:00:00, end 00:00:30).
- Nothing yet: no summary and no transcript. Ignore these.

For each meeting with a summary ready:
1. Get the summary and the tasks from FinMate. If the meeting's CRM sync info already lists Redtail, skip it.
2. Find the matching contact in Redtail. Use the contact already linked in FinMate if there is one; otherwise match on the attendee's name and email. If there is not exactly one confident match, do not guess: skip the meeting and list it as skipped.
3. Tasks first. Start each task's description with the line "FinMate meeting ID: <the meeting's id>". Before creating a task, search that contact's Redtail activities for one with the same ID line and title, and skip any that already exist. Create the rest as Redtail activities on that contact. If the meeting has no tasks, skip this step.
4. Then the note. Start it with the line "FinMate meeting ID: <the meeting's id>" and save it to that contact in Redtail. Do this last, and only if step 3 fully succeeded, because Redtail notes can't be searched for duplicates.
5. Only if the tasks (if any) and the note were all saved: in FinMate, link the contact to its Redtail record and mark the meeting as sent to my CRM, with notes and tasks recorded together in one update. If anything failed, do not mark the meeting as sent; list it as failed so the next run retries it.

For each meeting with a transcript only: do not save anything to Redtail and do not mark it as sent. Just list it, so I can pick a meeting type in FinMate to produce its summary and tasks. A later run will pick it up once it has a summary.

Do not edit or delete anything else in Redtail. When you are done, reply with up to four short lists, leaving out any that are empty:
- Saved to Redtail: meeting, contact, and what was saved.
- Needs a meeting type in FinMate: meeting and date.
- Skipped, no single Redtail match: meeting and attendee.
- Failed, will retry next run: meeting and what went wrong.
If there was nothing to do, say so.

Meetings that are still waiting for a meeting type are not marked as sent, so they show up in the list on every run until you pick one.

The routine looks back 7 days. Change that number in the prompt if you want a longer or shorter window.

How duplicates are avoided​

Marking a meeting as sent to your CRM is what lets the routine know where it left off, so a finished meeting isn't saved twice. Three things keep a half-finished one from creating duplicates when the routine retries it:

  • The meeting is only marked once everything is saved. Marking it after the tasks but before the note would hide a failed note forever, because marked meetings drop out of the "not sent yet" search.
  • Tasks are written first and checked. Each task carries a "FinMate meeting ID" line, and the routine looks for it in the contact's Redtail activities before creating anything. So if the note fails, the retry doesn't create the tasks again.
  • The note is written last. The Orion connector can create notes but can't search them, so the routine can't check for an existing one. Writing it last means it is only ever written once all else has succeeded.

One small gap remains: if the routine is cut off after saving the note but before marking the meeting, the next run saves that note again. To close it, see Optional: save the notes as an activity. Redtail activity search is also less certain than FinMate's own records, so check the first few runs.

Optional: save the notes as an activity​

By default the routine saves the meeting notes as a regular Redtail note, which shows on the contact's Notes tab. The Orion connector can create notes but can't search them, so that's the one thing the routine can't check for duplicates.

If you'd rather have stronger protection, save the notes as a Redtail activity instead, such as an appointment. Activities can be searched, so the routine can check for the meeting ID before writing, the same way it does for tasks. The trade-off is that the notes then appear in the contact's activity history rather than on the Notes tab.

To use it, replace steps 3 and 4 of the prompt above with:

3. Start each task's description, and the meeting notes, with the line "FinMate meeting ID: <the meeting's id>". Search that contact's Redtail activities for that ID line, and skip anything that already exists. Create each missing task as a Redtail activity (a task) on that contact.
4. Save the meeting notes as one Redtail activity on that contact (an appointment), with the meeting title as the subject and the notes as the description, dated at the meeting's start and end time. Skip this if an activity with that ID line already exists.

Leave step 5 as it is. Because both the tasks and the notes can now be checked, a retry after a failure or a cut-off run won't create duplicates of either.

Tips​

  • Run it once by hand first. Use the routine's run-now option, or paste the prompt into a chat, and check the notes and tasks in Redtail before you let it run on a schedule.
  • Pick a meeting type for waiting meetings. If a meeting shows up under "Needs a meeting type in FinMate", open it in FinMate and choose a meeting type. Once the summary and tasks are produced, the next run saves it to Redtail.
  • Check the skipped list. Meetings with no clear Redtail match are skipped and reported, not guessed. Link the contact in FinMate and the next run will pick it up.
  • Connectors must stay connected. If a connector's sign-in expires, the routine can't read or write until you reconnect it.
  • Changing the schedule. Edit the routine's schedule any time. The prompt doesn't depend on how often it runs.