MyASP Zapier integrationAutomate MyASP with Zapier.
The MyASP Zapier integration gives you 1 trigger, 1 action and 0 searches. A new customer in MyASP can start a Zap straight away, and a Zap can add a customer to MyASP from another tool with just an email address. Here is what it costs and what can break.
Verified Trustpilot reviews · AI, automation & growth agency
What the MyASP Zapier integration does
MyASP gathers in one place the tools a business needs to sell online. Linked to Zapier, its customer list stops being an island: each new customer can be passed to your other tools the moment it is created, and customers coming from elsewhere can be added to MyASP without typing them in. If Zapier is new to you, start with our Zapier review.
Every new customer, in your CRM at once. New Customer is an instant trigger: MyASP warns Zapier itself when a customer is created, so the copy in your CRM does not wait for a timer, even on the free plan.
A team that knows who just signed up. The same trigger can post a message in your team chat right after the CRM step, so someone on the team can follow up while the customer is still fresh in mind.
Customers from other tools, added to MyASP. Create Customer needs only an email address to create the customer. A form, a spreadsheet or another app holding that address is enough to feed it.
What Zapier does not do here. There is no search step, so a Zap cannot check whether a customer already exists in MyASP before creating one. There is no action to update or delete a customer either, and only one trigger: other events inside MyASP do not reach Zapier. To compare platforms on criteria, see n8n vs Zapier.
Zapier words in one minute
Seven terms come back on this page. Each one in plain words.
- Zap
- The automation you build on Zapier: 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. Once the Zap is on, Zapier waits for it. Here, a new customer in MyASP.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a customer.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
- Filter
- A step that lets the Zap go 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, a filter or a search makes one, and it needs a paid plan.
What a MyASP Zap really costs
MyASP is not reserved for paid plans: it works from the free plan. What Zapier bills is tasks.
- Free plan100 tasks a month, unlimited two-step Zaps
- TriggerNever billed
- Each successful action1 task
- Failed actionNot counted
New Customer never costs a task. Each action that succeeds counts one, whether it is Create Customer or a step in another app; one that fails is not counted. The free plan builds Zaps of two steps only, so adding a team message after the CRM step makes the Zap multi-step, which needs a paid plan. The interval grid below concerns polling triggers. It does not apply to New Customer, which is instant, nor to the trigger of another app when that one is instant too.
Connect MyASP to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your MyASP account linked once, then reused by every step that needs it.
- 02
Pick MyASP
Search for MyASP by name in the dialog, select it in the results, then click Add connection. A new tab opens, this time on the MyASP side, for the sign-in.
- 03
Sign in and grant access
Sign in to MyASP in that tab and grant Zapier access. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: new customers to your CRM, with a heads-up
GoalEach new customer created in MyASP becomes a contact in your CRM, then a message tells the team in your chat.
- 01
Create the Zap
Start a new Zap, choose MyASP as the trigger app and New Customer as the event, then pick your connection and give the trigger its Label Name.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the fields on a real customer rather than a blank one.
- 03
Add the CRM step
Add an action with your CRM and its create-contact event, then map the customer values into the contact fields. Check at test which values the trigger returned.
- 04
Add the team message
Add a second action with your team chat and write the message from the same values. Two actions make it a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each step, check the new contact and the message, then click Publish. For guided practice, see our Zapier training.
The MyASP trigger
1 event starts a Zap when something happens in MyASP, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Customer
Instant triggerIn Zapier“Triggers when a new customer is created.”
Starts your Zap each time a customer is created in MyASP and passes that customer's details to the next steps. It is the only way, through Zapier, for something that happens in MyASP to reach another tool, so every outbound flow from the app begins here.
The MyASP action
MyASP gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Customer
ActionIn Zapier“Create a new Customer”
Adds a new customer to MyASP from an email address taken from another step of the Zap.
When a MyASP Zap breaks
Zapier links no help article and no specific limit to MyASP. What can go wrong comes from how Zapier works in general and from the required fields.
Four cases are worth knowing before you publish. If a Zap behaves oddly, start with our Zapier troubleshooting page.
Existing customers stay where they are
A Zap only reacts to what happens after it is switched on. Customers created before publishing are not sent anywhere; moving that list is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again and burn through tasks.A bulk import at once
If a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.No email, no customer
Create Customer requires an email address. If the step before does not provide one, the action has nothing to fill its only required field with.
Need help automating MyASP with Zapier?
A person reads every message.



