STEP 1
Connect BombBomb and Forager
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
BombBomb and Forager Integration
Keep BombBomb and Forager in sync by integrating their events and actions. When sales events happen in BombBomb, update the Forager automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about BombBomb and Forager
Detailed info you need to know about BombBomb and Forager integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect BombBomb to Forager
Set up your BombBomb and Forager integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected BombBomb and Forager nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between BombBomb and Forager. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between BombBomb and Forager work in WEXTL?
WEXTL exposes actions and triggers for BombBomb and Forager that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
BombBomb triggersForager actions
BombBomb modules
- Add Contacts to a ListAdds contacts to a specified list.
- Create a ContactCreates a new contact.
- Delete a ContactDeletes an existing contact.
- Get a ContactRetrieves contact details by id.
- Get Contacts from a ListRetrieves contacts from a specified list.
- Make an API CallPerforms an arbitrary authorized API call.
- Remove Contacts from a ListRemoves contacts from a specified list.
- Suppress a ContactSuppresses the provided contact by id.
- Update a ContactUpdates an existing contact by id.
- Watch EventsTriggers when any event occurs.
Forager modules
- Get Work EmailPerforms a reverse lookup to find work emails associated with a person.
- Lookup a Person by PhonePerforms a reverse lookup of person details by phone.
- Lookup Personal EmailsPerforms a reverse lookup of personal emails for a person.
- Lookup Phone NumbersPerforms a reverse lookup of phone numbers to identify associated person details.
- Make an API CallPerforms an arbitrary authorized API call.
- Search a Person by EmailPerforms a reverse lookup of person details using an email address.
- Search Job Post EventsSearches for job post events.
- Search OrganizationsSearches for organizations.
- Search Website DetailsPerforms a reverse lookup of a website.
Frequently asked questions
Common questions about connecting BombBomb and Forager.
Connect your BombBomb and Forager accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when BombBomb's "Watch Events" fires, WEXTL can "Get Work Email" in Forager. BombBomb has 1 trigger (including Watch Events); Forager has 9 actions (including Get Work Email, Lookup a Person by Phone, and Lookup Personal Emails). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. BombBomb-to-Forager automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment BombBomb (or Forager) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your BombBomb + Forager automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the BombBomb and Forager integration.
- BombBomb and Forager integration source code, module specs and credentials implementation.
- Our BombBomb and Forager integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BombBomb and Forager — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- BombBomb integration information
- Forager integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library