Integrating MINDBODY with Pinecone by AI Agents and Assistants

Triggers when a new staff appointment created

Triggers when a staff appointment updated

Triggers when a class Description is updated

Triggers when a Class Roster Booking status is updated

Triggers when class schedule is updated

Triggers when a class is updated

Trigger when a client contact logs.

Triggers when a new client contract is created.

Triggers when a Client Contract is updated

Triggers when a new class is created

Triggers when a new class booking is created.

Triggers when a new class visit is created.

Trigger when a new client indexes.

Triggers when a new client purchases is created.

Triggers when a new contract is created.

Triggers when a new enrollment is created

Triggers when a new product created

Triggers when a new registrant is created.

Triggers when a new sale is created. (min 4 api calls + api calls depending upon count of purchased items)

Triggers when a new staff appointment created

Triggers when a staff is updated

Triggers when a new product inventory is updated

Triggers when new registrant added or an existing registrant is updated.

Trigger when a new collection is create.

This operation returns a list of your Pinecone indexes.

Action when a new appointment created (max 2 api calls per task)

Cancel a existing appointment (max 2 api calls per task)

Creates a new sale (max 3 api calls per task)

Create a new user or updates an existing user (max 3 api calls per task)

Create New User (max 2 api calls per task)

Purchase account credit (max 2 api calls per task)

Creates a new purchase contract (min 2 api calls per task)

Creates a new gift card (max 2 api calls per task)

Remove client from class (max 2 api calls per task)

Remove client from existing class booking (max 2 api calls per task)

Action when an appointment updated (max 2 api calls per task)

Delete an existing sale (max 2 api calls per task)

This operation creates a Pinecone collection.

This operation creates a Pinecone index. You can use it to specify the measure of similarity, the dimension of vectors to be stored in the index, the numbers of replicas to use, and more.

The Delete operation deletes vectors, by id, from a single namespace. You can delete items by their id, from a single namespace.

The Fetch operation looks up and returns vectors, by ID, from a single namespace. The returned vectors include the vector data and/or metadata.

The Query operation searches a namespace, using a query vector. It retrieves the ids of the most similar items in a namespace, along with their similarity scores.

The Update operation updates vector in a namespace. If a value is included, it will overwrite the previous value. If a set_metadata is included, the values of the fields specified in it will be added or overwrite the previous value.

The Upsert operation writes vectors into a namespace. If a new value is upserted for an existing vector id, it will overwrite the previous value.