Resources · Zapier integration

Morphais Zapier integrationAutomate Morphais with Zapier.

The Morphais Zapier integration has 1 trigger, no action and no search. That single trigger, New Startups, is a polling one: Zapier checks Morphais at your plan's interval and passes each newly published startup to the tools you choose. Here is how to use it well and what it costs.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Morphais Zapier integration actually does

Morphais is a data platform that publishes (pre-)seed startups and founders still in stealth. The integration plugs it into Zapier, so a Zap (the automation you build on Zapier: one trigger, then one or more actions that run each time it fires) can carry each new startup into the tools your team already reads.

Everything starts from one trigger, so the results come from what you put after it. Three examples. A running list: each startup Morphais publishes becomes a row in your spreadsheet, where the team can sort and comment. A pipeline that fills itself: the same startup opens a record in your CRM, ready for someone to qualify it. A shared alert: a message in your team chat, so nobody has to open Morphais to know something new came in.

What Zapier does not do here matters as much. Morphais offers no action on Zapier, so a Zap cannot write anything back into Morphais: no tag, no note, no status. There is no search step either, so a Zap cannot look up a startup that was published earlier. And the trigger only sees startups published after the Zap is switched on. The trigger is a polling one too, so a new startup reaches your tools at the next check, not the moment Morphais publishes it.

For the basics of building Zaps, see our Zapier training.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this page. Each one is explained once, here, then used as is.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. For Morphais, the only one is a new startup being published.
Action
What the Zap does once it has started: the step that writes or sends something. With Morphais, actions live in your other tools.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, the moment the event happens. Morphais has none, so its trigger always waits for the next check.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
Cost

What it really costs

Morphais is not a premium app, so it works from the free plan. You pay in tasks, and the trigger itself is free.

  • Free plan100 tasks a month, unlimited two-step Zaps
  • Trigger checksNever billed
  • Successful action1 task each
  • Premium appNo

Checking Morphais for new startups never costs a task, however often Zapier looks. Each action that succeeds in your other tools counts once, so one startup sent to a sheet and to a chat uses two tasks, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps. The interval grid below sets how often New Startups is checked on each plan.

Connect

Connect Morphais to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page and click + Add connection. A connection is your Morphais account linked once, then reused by every Zap that starts from Morphais.

  2. 02

    Pick Morphais

    Search for Morphais in the dialog, select it and click Add connection. You need an account on Morphais, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and allow access

    A tab opens on Morphais. Sign in with your account and grant Zapier access to it. The tab closes, and the connection is ready to use as the trigger of your first Zap.

First Zap

Your first Zap: new startups straight into your CRM

GoalEach startup Morphais publishes opens a record in your CRM, but only when it meets the condition you set in a filter.

  1. 01

    Pick the Morphais trigger

    Build a new Zap, choose Morphais as the trigger app and New Startups as the event, then select the connection you made above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent startups of the connected account, so pick a real one and look at the fields it carries.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and set the field to look at, the rule and the value. A filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the CRM action

    Choose your CRM and its action to create a record. Map each CRM field to a value from the Morphais sample, one field at a time, then test the step.

  5. 05

    Publish

    Read the record the test created in your CRM. If it looks right, publish the Zap to switch it on; from then on, Zapier checks Morphais at your plan's interval.

Triggers

The Morphais trigger

1 event starts a Zap when something happens in Morphais. Zapier checks for them at the interval your plan allows.

1

New Startups

Polling trigger

In Zapier“Triggers when new startups are published by Morphais.”

Hands your Zap each startup Morphais publishes, one at a time, so the next steps can record it, route it or announce it in another tool. It is the only door into Morphais data on Zapier.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your team tracks newly published startups in a sheet, a CRM or a chat channel and wants them there without opening Morphais.
Watch out
the fields that come with each startup are not listed anywhere outside the editor, so run the test and read the sample before mapping or filtering on any of them.
When it breaks

When a Morphais Zap breaks

Zapier attaches no help article to Morphais, so the known failure points are the general ones of any Zap built on a polling trigger.

Read these three cases before you publish. If a Zap still stops, our Zapier troubleshooting page is the next place to go.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Startups published earlier are not picked up; moving that backlog is a separate job.
  • A large batch held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.
  • The same startup, once

    On a polling trigger, Zapier keeps track of what it has already seen, so the same startup does not start the Zap twice.
Need help

Need help automating Morphais with Zapier?

A person reads every message.

FAQ

Morphais Zapier integration: questions

01Is the Morphais Zapier integration free?
Yes, for two-step Zaps. Morphais is not a premium app, so it runs on Zapier's free plan, which gives 100 tasks a month and an unlimited number of Zaps. Each free Zap is one trigger and one action: New Startups, then one step in another tool. If you want each startup both in a sheet and in your chat, or want a filter in front, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Morphais Zap use?
One task per successful action, and the trigger is free. Since Morphais has no action of its own, every task is spent in your other tools: one startup sent to a spreadsheet uses one task, sent to a sheet and a CRM it uses two. An action that fails is not counted. Your monthly use is the number of startups that reach the Zap multiplied by its actions, so a filter in front is a way to keep that number down.
03Does the Morphais trigger work in real time?
No. New Startups is a polling trigger, so Zapier goes to check Morphais at a fixed interval. On the free plan that is every 15 minutes, on Professional every 2 minutes, and on Team and Enterprise every minute. On paid plans you can also change how often the trigger checks, or run a check by hand from the editor. None of these checks costs a task, however often they run.
04What does it take to connect a Morphais account?
An account on Morphais, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of Zapier you add a connection, pick Morphais, sign in in the tab that opens and grant Zapier access. That connection is then reused by every Zap that starts from New Startups, so it is a one-time step per account. When you test New Startups, Zapier brings back the three most recent startups of the connected account.
05Can a Zap update or tag startups inside Morphais?
No. Morphais offers no action on Zapier, only the New Startups trigger, so data flows one way: out of Morphais and into your other tools. Whatever your team adds to a startup, a note, a status or an owner, lives in the CRM or the sheet you send it to. If writing back into Morphais matters for you, that is a limit of this integration to weigh before building around it.
06What if the Morphais operation you need is not there?
Open the Morphais page on Zapier: it shows the current list of triggers and actions, and today that list is the New Startups trigger alone. Anything else, such as fetching older startups or acting on one inside Morphais, cannot be built with this integration. One way around is to do the work in the tool that receives the startup, where the actions you need may already exist. Check that tool's own options.
07Zapier, Make or n8n for Morphais?
Choose on criteria rather than on a ranking. Check first whether Morphais is offered in the other tool at all; on Zapier it is, with one polling trigger. Then look at the delay you can live with: on Zapier it depends on your plan, from 15 minutes on the free one down to one minute. Last, count the actions you will chain after the trigger, since Zapier bills one task per successful action.