- Home
- Resources
- Integrations
- Medullar
Medullar Zapier integrationAutomate Medullar with Zapier.
Medullar Zapier integration: 5 actions and 1 search to create, rename and delete Spaces, add records to them and ask them questions, all started by an event in another app, since Medullar has no trigger of its own on Zapier.
Verified Trustpilot reviews · AI, automation & growth agency
What the Medullar Zapier integration does for you
The Medullar Zapier integration lets Zapier, an automation service, work inside your Medullar Spaces when something happens elsewhere. Medullar is an AI platform built around Spaces that hold your knowledge. Through Zapier you can feed those Spaces, question them and keep them organised, without opening Medullar.
Spaces that fill themselves. Add a Record to a Space pushes new knowledge into a Space each time something arrives in another tool, such as a form answer or a new row. The Space grows without anyone copying and pasting.
Questions asked on cue. Ask Space sends a message to a Space, which answers from the knowledge it holds. Wire it after a trigger in another app and the question goes out on its own; check at the test what comes back before using it in a later step.
A tidy list of Spaces. Create Medullar Space, Rename a Space and Delete a Space follow the life of a project in another tool, so your Spaces mirror the work that is actually going on.
What Zapier does not do here: Medullar has no trigger, so nothing that happens in Medullar can start a Zap. Every Zap begins in another app, and there is no find-or-create shortcut on its one search. To weigh Zapier against other tools for this, see our n8n vs Zapier comparison.
Zapier words, in one minute
Eight words come back all over this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Medullar has none on Zapier, so the trigger always comes from another app.
- Action
- What the Zap does once started: the step that writes, sends or moves something, like adding a record to a Medullar Space.
- Task
- The unit Zapier bills. One action that your Zap completes successfully is one task, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer; an instant one is reported by the app at once. Here, it depends on the other app's trigger.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What a Medullar Zap really costs
Medullar is not one of the apps Zapier keeps for paid plans: it works on the free plan.
- Free plan100 tasks a month, unlimited two-step Zaps
- Medullar actionOne task each time it succeeds
- Failed actionNot counted against the plan
- Find List_space or filterMakes the Zap multi-step: paid plan
Each Medullar action that succeeds counts as one task, and one that fails is not billed. The trigger, from your other app, costs nothing. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps. Add Find List_space, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Medullar has no trigger, so the interval grid below depends on the trigger you pick in the other app: it only applies if that one is a polling trigger.
Connect your Medullar account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Medullar account, plus read or write access on any Space you do not own yourself but want the Zap to touch.
- 02
Pick Medullar
Type Medullar in the search box of the dialog, select it, then click Add connection at the bottom of it. A new browser tab opens on the Medullar side.
- 03
Sign in and grant access
Sign in to Medullar in that tab and allow Zapier to use the account. The connection is saved once, and from then on every Medullar step of every Zap reuses it.
Your first Zap: ask a Medullar Space about each new form answer
GoalEach new form submission is turned into a question for your Medullar Space, and the reply goes out by email from your mail tool.
- 01
Build: start in the other app
Create a Zap and pick your form tool and its new submission event as the trigger. Medullar has no trigger, so the Zap always starts outside it.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent submissions, so you build the question on a real answer rather than a guess.
- 03
Add Ask Space
Click the plus icon, pick Medullar and Ask Space. Select the Space, the chat mode and the reasoning effort, then map the submission into the message.
- 04
Add the email step
Add your mail tool and map what Ask Space returned into the email. Check at the test what that step actually sends back. Two actions make this Zap multi-step.
- 05
Test, then publish
Run each step once and read what came back. Then click Publish. Only submissions received after that point will reach the Space.
Medullar actions
Medullar gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add a Record to a Space
ActionIn Zapier“Add a new record to a Medullar Space. This will add a new knowledge in the specified space.”
Puts a new piece of knowledge into the Space you select, so it can be used in later answers.
Ask Space
ActionIn Zapier“Ask a question to a Medullar Space. This will use knowledge in the specified space.”
Sends a message to a Space, which answers from the knowledge stored in it.
Create Medullar Space
ActionIn Zapier“Create a new Space in Medullar.”
Opens a new Space in Medullar under the name you give it, ready to receive records and questions.
Delete a Space
ActionIn Zapier“Deletes an existing Space from Medullar.”
Removes an existing Space from Medullar, the one you select in the step.
Rename a Space
ActionIn Zapier“Renames an existing Space in Medullar.”
Gives an existing Space a new name, without touching what it holds.
Medullar search
1 search step looks for data that already exists in Medullar, so a later step can use it.
A search step finds something that already exists in Medullar and passes it on. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not what you expected.
Find List_space
SearchIn Zapier“Finds a list_space based on name.”
Looks up by name the item Zapier calls list_space and hands it to the steps that follow.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that needed it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, ticking it turns a search into a find-or-create. Medullar's search shows no such variant in the editor.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Medullar Zap breaks
Zapier attaches no help article to Medullar, and no limit specific to the app is documented. What breaks is what breaks on any Zap.
Four cases are worth knowing. When a run looks wrong, rerun the step test and read what came back, then see our Zapier troubleshooting guide.
Old items never reach Medullar
A Zap only reacts to what happens after you publish it. What already sat in the other app is not replayed, and moving that backlog is a separate job.The search finds nothing and the Zap stops
By default, a Find List_space that comes back empty stops the Zap and skips the steps after it. Switch the setting on if the Zap should go on anyway.The Zap keeps restarting itself
A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count fast.A bulk import goes quiet
When the trigger in the other app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back.
Need help automating Medullar with Zapier?
A person reads every message.



