Connecting with an AI Agent

You can let an AI assistant work with your Puree account, so that when you ask it a question about your business it fetches the real answer from your data instead of guessing at one. “Agent” and “assistant” mean the same thing here: Claude, ChatGPT and the like. This page is the plain-English version. If you or the person helping you wants the technical detail, that’s on The Developer API.

There are two ways to connect:

• Sign in to Puree. You add Puree to your AI app as a connector, click Sign in to Puree, sign in as you normally would and choose what to share. There’s nothing to copy or paste. This is the way we recommend for almost everyone, and it’s what most of this page covers.
• An access token. A long password you create in Puree and paste into a tool. This is the route for scripts, Zapier, a custom GPT, or an assistant that can’t use Sign in to Puree yet. It’s covered further down, under Connecting With an Access Token Instead.

What It Can and Can’t Do

You decide, person by person and area by area, what can be reached, and for each area whether an assistant may only look things up or change them too.

What an assistant can do:

• Look things up in Orders (and the notes on them), Customers, Items and categories, Packages, Staff, the Delivery run sheet, Who works each shift, Supplier deliveries and collections, Dockets, Commentary and email templates, Tasks, Enquiries, Tags and Recipes. That’s enough to answer questions like which quotes are expiring in the next fortnight, what’s on tomorrow’s run sheet, what you sold most of last winter, or which items are flagged as containing nuts.
• Change items and categories, and packages. An assistant with that access can, for example, tidy up item names, fix prices or reorder your menu.
• Customers: adding and updating customers, their contacts and their delivery addresses, for example “add the contact details from this email to Acme Events”. A contact needs at least one of an email or a phone, so someone known only by name and number can be added too. It can archive or restore a customer, and turn Can pay on invoice on or off, but only when you ask. It can also keep files against a customer, such as a contract or a floor plan; those are for your team and the customer doesn’t see them. An assistant can’t resubscribe anyone who has unsubscribed from your emails.
• Tasks: looking up your follow-ups, adding new ones (“remind me to call the venue on Friday”) and marking them done.
• Quotes: adding a note to a quote (“note that the bride’s mother is allergic to shellfish”), setting the chef and driver instructions that print on its dockets, and attaching or removing documents. A document it attaches shows on the customer’s view of the quote straight away. It can’t create, price, accept or cancel a quote.
• Past orders: bringing across orders from before Puree, for example from your old system’s PDFs. Each one is filed against the right customer with its PDF, as history: it never becomes a quote and never appears in reports, the calendar or dockets. See Bring your past orders across with AI.
• Shifts: putting your staff on a quote’s shifts or taking them off (“put Sam on the bar shift for Saturday”). Not for accounts that roster through Deputy.
• Delivery run sheet: planning a day’s deliveries (“put Sam on run 2, leaving at 7.30”) and adding or renaming drivers. Deliveries themselves come from your quotes.
• Supplier deliveries and collections: recording how hired or bought-in goods arrive and go back for a quote. It never emails the supplier; you still send the order from Puree.
• Dockets: fetching a quote’s chef, driver, equipment or beverage docket, event brief, consolidated docket or quote, or a day’s run sheet, as a PDF (“send me the chef docket for Friday’s wedding”). Some AI apps can’t show a PDF and offer it as a download instead.
• Commentary and email templates: looking up and editing the wording you reuse on quotes and emails. A change reaches every quote or email that uses the template from then on. Your terms and conditions stay in Puree.
• Photos: adding or replacing the photo on an item or a package from a picture you give the assistant.
• Enquiries and opportunities (with their tags and notes), tags, newsletter groups, staff (the people who work your events) and recipes and ingredients, plus the menu headings, presentation styles and suppliers your items and packages refer to, and the venue types your quotes can carry.

Some rules always hold:

• A connected app only ever gets what you’ve been given. If the owner has given you read access to items but not write, an app you connect can read items but not change them.
• An assistant can’t create, price, accept or cancel a quote, send emails, or delete records other than a past order. There is no setting that allows it. On a quote it can only add notes, set the chef and driver instructions and attach or remove documents, if you allow it. Records an assistant can change are made inactive, archived or completed rather than deleted. The only removals are taking a contact out of a newsletter group, taking a person off a shift, unlinking a document from a quote, removing a customer’s document, and deleting a past order or removing its PDF. The contact, the person and a quote’s document (in your library) all stay, and a removed customer document or past-order PDF can be restored in Puree. Deleting a past order deletes the record itself; only its PDFs can be restored.

Every action an assistant takes is recorded in the Activity log, in plain English, so you can always see what it did. Read the full story in API and AI Access: Decide Who Can Connect AI to Your Puree Account.

Before You Start

• Your account needs to be on the Professional plan. API and AI access, including connecting AI apps, is part of the Professional plan. If you’re on Professional and don’t see API and AI access under Settings, email email@puree.app and we’ll turn it on for you.
• The account owner decides who can use it. Admins don’t get access automatically; they need to be given it by the owner, like anyone else.
• The owner must accept the terms once. They explain that connected tools act on your behalf, that AI can make mistakes, and that Puree isn’t responsible for outside AI systems. If the owner hasn’t accepted the current terms, nobody on the account can connect a new app.
• Two-factor authentication (2FA) must be on for anyone connecting an app or creating a token. See Two-Factor Authentication.

Connecting With Sign in to Puree

1. Add Puree to your AI app as a connector. In your AI app’s settings, add a new connector and give it this address:

https://mcp.puree.app/mcp

In Claude, go to Settings → Connectors, click Add, then Add custom connector. Name it Puree, paste the address above and click Add. Then click Connect next to Puree.

In ChatGPT (at chatgpt.com, not the desktop app):

1. Open Settings and go to Plugins. If you can’t see it, type plugins in the Settings search box.

2. Click Add, then Create custom MCP server.

   

3. Name it Puree, leave Server URL selected and paste the address above. Leave Authentication on OAuth and don’t change the advanced OAuth settings. Tick I understand and want to continue, then click Create as a plugin.

   

4. Click Connect. You’ll see the Puree connector’s page, which names ChatGPT and shows you’ll be sent back to chatgpt.com. Click Sign in to Puree and carry on from step 3 below.

   

Some ChatGPT plans don’t offer custom MCP servers. If you don’t see the option, check your plan or use an access token instead (see Connecting With an Access Token Instead below).

In Grok:

1. Open Plugins (bottom left), go to the Connectors tab and click New Connector.

2. Choose Custom.

   

3. Name it Puree, paste the address above as the Server URL and click Add Connector. Then connect it and click Sign in to Puree, carrying on from step 3 below.

   

2. Click Sign in to Puree. Your AI app opens a page headed Connect followed by your app’s name, showing the address you’ll be sent back to when you’re done. Only carry on if you started this yourself from that app. If you didn’t, close the page. Then click Sign in to Puree.

3. Sign in. If you haven’t signed in to Puree in the last 15 minutes, you’ll be asked for your email and password first. If you entered a code from your authenticator app in the last 5 minutes, for example because you’ve just signed in, you go straight to the next step. Otherwise Puree asks for one code (or a backup code) before you carry on, so that nobody can connect an app with a browser you happened to leave signed in.

4. Check the Connect to Puree page. It shows:

• Which app is asking, with the address it’s connecting from (for example “Connecting from claude.ai”). This is what the connector reported; check it matches the app you’re using.
• The account. If you belong to more than one Puree account, pick the one to connect.
• Access. Each area the app is asking for, both looking up and, where it can, changing, ticked. Untick anything you’d rather not share, such as the changing ones if you only want answers. An area the owner hasn’t given you on this account is shown crossed out, as “Not shared with you on this account”.
• Staff includes people’s details. Read staff lets the app see your staff roles and rates and the people who work your events, with their names, phone numbers and email addresses (never their pay); Change staff lets it add people and change their details. Untick them if you’d rather the app didn’t have your staff’s details.

5. Click Allow. You’re sent back to your AI app and it’s connected. Click Cancel at any point instead and nothing is connected.

6. Ask it something. From here you talk normally. The assistant works out which lookup answers your question, fetches it from Puree and reads the result back to you.

Seeing and Disconnecting Connected Apps

Go to Settings → API and AI access. Under Connected apps you’ll see each app connected to the account: the app and its address, who connected it, what it can do, when it was connected, when it was last used, when it ends, and whether it’s active or paused.

• Disconnect stops an app reaching Puree straight away. You can disconnect your own apps, and the owner can disconnect anyone’s.
• The owner sees every app connected to the account. Everyone else sees their own.
• Your connections on every account, at the bottom of the list, shows every app you’ve connected across all your Puree accounts. You can disconnect them there too, even from an account you no longer have access to.

How Long a Connection Lasts

A connection lasts up to 90 days, and ends sooner if the app hasn’t used it for 60 days. When it ends, reconnect from your AI app by running through the steps above again.

A connection also ends straight away, without you doing anything, if:

• the owner takes away the access it was using, or removes you from the account;
• you change or reset your Puree password;
• your Puree login is deactivated or deleted.

Some things pause your connected apps rather than disconnecting them, and they work again as soon as the problem is sorted:

• you turn 2FA off (they resume when you turn it back on);
• API and AI access is switched off for the account (they resume when it’s switched back on);
• the owner hasn’t accepted updated terms in time (they resume once the owner accepts).

Connecting With an Access Token Instead

An access token is the route for anything that can’t use Sign in to Puree: your own scripts, Zapier or Make, a ChatGPT custom GPT, or an assistant that doesn’t support it yet. You’ll need two things:

1. An access token — a long password that identifies your account. You create it in Puree.
2. The schema address — https://puree.app/api-docs/v1/swagger.yaml. Think of it as a menu: it tells the assistant which questions it’s allowed to ask and what the answers look like. It’s the same for everybody and it isn’t secret.

1. Create your token. On Settings → API and AI access, add an access token. You’ll be asked for three things:

• A name. Something that says where it’s going, like “ChatGPT assistant”. If you later have several, this is how you tell them apart.
• Permissions. Tick what this token may read or change. You can only tick what the owner has given you, so if a box is missing, ask the owner. Tick only what the tool actually needs.
• An expiry. Optional. Leave it blank and the token lasts until you revoke it, or set a date and it stops working by itself. A date is the safer choice if you’re only trying something out.

The token appears once, on the screen straight after you create it. Copy it then. If you lose it you can’t look it up again, but you can always revoke it and make another.

2. Put the token into your tool’s settings — not into the chat. Any tool built to connect to an outside service has a proper place to store a credential, separate from the conversation. In a ChatGPT custom GPT, for example, it’s under Actions → Authentication: choose API Key, set the type to Bearer, and paste the token there. The Puree connector also still accepts a pasted token, under Or paste a Puree access key on the page where you’d otherwise click Sign in to Puree.

3. Give it the schema address in whatever field your tool calls “schema”, “OpenAPI URL” or “import from URL”. (The Puree connector doesn’t need this.)

What About Zapier and Similar Tools?

Yes, with one caveat about how it has to be set up.

There’s no ready-made Puree app in Zapier’s directory yet, so you won’t find us by searching. What you use instead is Zapier’s own Webhooks step: add a GET request, put the address of what you want in the URL, and add a header called Authorization with the value Bearer followed by your token. That’s the same token and the same secrecy rules as everywhere else on this page. Zapier’s Webhooks step is a premium one, so it needs a paid Zapier plan. Make.com does the same job with its HTTP module, which is on its free tier.

The caveat is which way round it works. Puree doesn’t yet send a signal out when something happens, so nothing in Puree can start a Zap by itself. Instead you use Zapier’s Schedule trigger to go and look on a timetable. A Zap that runs at seven each morning, fetches the day’s orders and posts a summary into Slack works nicely. A Zap that fires the instant a customer accepts a quote isn’t possible yet.

A Zap can only do what its token allows. A token with read access can pull information out of Puree; to let it change anything (items, packages, customers, tasks, enquiries, the run sheet or any other area), the owner has to give that person write access to that area first. Anything it sends must be JSON.

Keeping Things Secure

With Sign in to Puree there’s no token for you to look after: your AI app never sees your password, and you can disconnect it at any time. A few habits still matter:

• Only click Allow for a request you started yourself, from an app you recognise, at the address you expect.
• Share only what the assistant needs. Untick anything it doesn’t, and leave off the changing ones unless you want it to make changes.
• If you share a chat or a custom GPT with others, they may see what the assistant read from your account. Keep an assistant connected to your business data private to you and your team.
• Check the Activity log now and then. It lists everything done through a connection, with who, when and what, so something happening at a time you weren’t working is a signal worth acting on.
• Disconnect or revoke the moment you’re suspicious, or when someone leaves, or when you stop using a tool. It takes effect immediately.

If you use access tokens, treat each one exactly as you’d treat your Puree password. Anyone holding it can use the access it carries, from anywhere, without signing in as you.

• Don’t email it, don’t put it in a shared document, and don’t paste it into a chat message.
• Use a separate token for each tool. If one needs replacing you revoke just that one, and everything else keeps working.
• Give each token only what it needs. Read-only is the safest place to start.
• If you publish a custom GPT, everyone who uses it is using your token and seeing your account’s data.

If the owner narrows someone’s access, their existing tokens are narrowed straight away, and removed if nothing is left. And if someone turns 2FA off, their tokens are paused (not deleted) until they turn it back on.

A Couple of Limits

A connection or token only ever sees the one account it was connected to — there’s no arrangement under which an assistant could reach another caterer’s data, or another caterer’s assistant reach yours. And each one can make 60 requests a minute, which is plenty for asking questions and getting answers, but not enough to pull down your entire history in one go.

We’re Happy to Help

You don’t have to work this out alone. If you’d like a hand getting an assistant connected, or you’re not sure whether the thing you want to ask it is possible, email email@puree.app and we’ll walk you through it, or set it up with you on a call. We’d rather do that than have you give up on it.