Lome Zapier integrationAutomate Lome with Zapier.
The Lome Zapier integration gives you 3 triggers, 1 action and 0 searches. A sign-up, an RSVP or a new community can start a Zap, and a Zap can add a contact to your Lome address book. Here is what it does, what it costs and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lome Zapier integration actually does
Lome is a tool for building simple sign-up forms for a community. Connected to Zapier, it reports three kinds of events (a response on one of your forms, a response inside a chosen community, a community you create) and it can add a contact to your Lome address book from anything another app sends.
Three results come out of it. An address book that fills itself: New Response starts the Zap and Create Contact files the person who signed up or RSVPed. A per-community list: New Community Response watches one community you pick and sends its sign-ups to a sheet or another tool, kept apart from the rest. A team kept in the loop: New Community fires when you set up a community to host or co-host, so the people who help run it hear about it.
What Zapier does not do for Lome. There is no search, so a Zap cannot check whether a contact is already in the address book before adding one. The only action creates a contact: nothing updates or deletes one, and nothing creates a form or a community. All three triggers are polling ones, so a response reaches the Zap at Zapier's next check. Responses collected before the Zap is published are not picked up.
Comparing platforms first? See our n8n vs Zapier comparison and our Zapier review.
Zapier words, in plain English
Seven terms come back on this page. Here is each one in a line.
- 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 a Zap. Once the Zap is on, Zapier waits for it: here a response or a new community.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like a new Lome contact.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and the number on your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer and keeps only what it has not seen. An instant one is reported by the app itself.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it there otherwise.
- Connection
- Your Lome account linked to Zapier once, then reused by every Lome step in every Zap you build after that.
What a Lome Zap really costs
Lome is not a premium app, so it works on the free plan. Its triggers never cost a task, however often Zapier checks: only an action that succeeds is billed.
- Triggers0 tasks, however often checked
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
A Zap that turns each response into a contact uses one task per response. Send a copy to a sheet as well and each response costs two. A failed action is not counted. The free plan gives 100 tasks a month and two-step Zaps only. A filter or a second action makes the Zap multi-step, which needs a paid plan. All three Lome triggers are polling ones, so the grid below applies to every one of them: it is how long a response can wait before Zapier picks it up.
Connect Lome to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A dialog with a search box appears. You need a Lome account first: Zapier only links to one that already exists.
- 02
Find Lome
Type Lome in the dialog, pick it from the results, then click Add connection. A new tab opens on the Lome side, where you sign in with the login you already use.
- 03
Grant access
Sign in and allow Zapier to reach the account. The connection is stored once and every Lome step reuses it. For a community you co-host, check first that your login can see its forms.
Your first Zap: file every sign-up as a contact
GoalEach person who signs up or RSVPs on your Lome form becomes a contact in your Lome address book, so the list you write to later is built without copying anyone by hand.
- 01
Build: pick the trigger
Create a Zap, choose Lome as the app and New Response as the event, then select the Lome connection you added on the Apps page.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next step on a real response rather than an empty one.
- 03
Add a filter if needed
Optional: set the field, the rule and the value, so only the responses you want go on. With a filter, the Zap becomes multi-step and needs a paid plan.
- 04
Map the contact
Add Create Contact and map the person's first and last name from the response into Contact Name, the one required field. Map the other fields you want to keep.
- 05
Test, then Publish
Test the action and look for the new contact in your Lome address book. Then click Publish. Responses arrive at the next check, at the interval your plan sets.
The three Lome triggers
3 events start a Zap when something happens in Lome. Zapier checks for them at the interval your plan allows.
New Community
Polling triggerIn Zapier“Triggers when you create a new Community to host or co-host.”
Fires when you create a new community to host or co-host in Lome, and passes that community to the next steps so other tools can be told about it.
New Community Response
Polling triggerIn Zapier“Triggers when someone signs up on a form inside a specific Community that you choose.”
Watches the forms of one community you choose, and starts the Zap each time someone signs up there, leaving every other community out of it.
New Response
Polling triggerIn Zapier“Triggers when someone signs up or RSVPs on your form.”
Each sign-up or RSVP on your form starts the Zap here, with the details of the response ready to map into the next steps, such as a new contact.
The Lome action
Lome gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a Contact in your Lome Address Book”
Adds a person to your Lome address book from data another step brings, whether a Lome response or a form, sheet or tool elsewhere.
When a Lome Zap breaks
Zapier attaches no help article and no rate limit to Lome. What goes wrong comes from how Zapier works, and from the one required field of the action.
Four cases cover most surprises. For anything else, our Zapier troubleshooting guide is the place to start.
Older responses never arrive
A Zap only reacts to what happens after it is published. Responses collected before that never go through it; moving them is a separate job.Responses seem late
All three triggers are polling ones. A response waits for Zapier's next check, at the interval of your plan, before the Zap starts.A big batch gets held back
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold the runs back instead of firing them all.No name for the contact
Create Contact requires Contact Name, a first and last name. If the step before carries no name to map, the action has nothing to fill it with.
Need help automating Lome with Zapier?
A person reads every message.
