Can I use Pabbly to send LeadSwift API data to Google Sheets?

[chris007]

Hi Pabbly team,

I’d like to automate a workflow where I pull new lead data from the LeadSwift API 0 https://leadswift.com/account/helpdesk/faq/i/How+can+I+use+the+API? and send it directly into Google Sheets using Pabbly Connect.

I then want google sheet to return new business leads (fields like business name, email, phone, location, website).

Let me know if this is achievable within Pabbly and how to go about it?

Thanks,
Chris

---

 

[ArshilAhmad]

Hi @chris007,

Currently, we don't have a direct integration with the application you have mentioned. If you would like this application to be added to Pabbly Connect, you can submit your request on our dedicated platform.

Connect: New Integration Request | Pabbly

Vote or request new Pabbly features. Subscribe to get updates about new features from Pabbly.

roadmap.pabbly.com

Our integrations team will review your request and, if possible, add the desired application to Pabbly Connect.

In the meantime, if the LeadSwift application supports webhooks, you can try using Webhook by Pabbly to capture the new leads.

You can then use 'Add New Row' action step to add data to your Google Sheets spreadsheet.

 

[chris007]

Thanks it doesn't support webhooks but you can export leads and import them into their platform.

It does have a LeadSwift REST API to automate your tasks.

This is on their documentation, surely there is a way to pull this via Pabbly?

How can I use the API?​

You can use the LeadSwift REST API to automate your tasks.
You can generate and manage your API keys here. A sample PHP file with the below functions can be downloaded here.
CAMPAIGNS
Get all campaigns list:
GET

https://leadswift.com/api/campaigns?api_key=[api_key]

Get campaign by ID:
GET

https://leadswift.com/api/campaigns/[id]?api_key=[api_key]

Create a campaign:
POST

https://leadswift.com/api/campaigns?api_key=[api_key]

• Params: title, description (optional)

Edit a campaign:
PUT

https://leadswift.com/api/campaigns/[id]?api_key=[api_key]

• Params: campaign_id, title, description (optional)

Delete a campaign:
DELETE

https://leadswift.com/api/campaigns/[id]?api_key=[api_key]

SEARCH QUERIES
Get searches of a campaign:
GET

https://leadswift.com/api/searches/[id]?api_key=[api_key]

Submit a search:
POST

https://leadswift.com/api/searches?api_key=[api_key]

• Params: campaign_id, keyword, location, search_html_code (optional)

Delete a search:
DELETE

https://leadswift.com/api/searches/[id]?api_key=[api_key]

GET LEADS OF A SEARCH
Get leads:
POST

https://leadswift.com/api/leads?api_key=[api_key]

• Params: search_id, start (Paging offset, the total offset is returned in [recordsFiltered] value), length (Number of leads per page), search[value], search[regex], custom_filter, exact_match_location, exclude_closed_location, merge_by_domain, exact_match_domain_only, social_profiles, whois, free_providers, cols[]

USER INFO, USER PACKAGES
Get user info:
GET

https://leadswift.com/api/user_info?api_key=[api_key]

USER SETTINGS
Get current settings:
GET

https://leadswift.com/api/user_settings?api_key=[api_key]

Update user settings:
PUT

https://leadswift.com/api/user_settings?api_key=[api_key]

• Params: notification_email, zerobounce_api_key, neverbounce_api_key, emaillistverify_api_key, mailtester_api_key, hunterio_api_key, debounce_api_key, zerobounce_api_enable, neverbounce_api_enable, emaillistverify_api_enable, mailtester_api_enable, verify_database contacts, hunterio_api_enable, debounce_api_enable, email_verification, email_verification_only_email, email_finder, disable_notification_email, audit_logo, audit_url, unsubscribe_url, trackmail_url, custom_global_blacklist_emails, maximum_emails_per business, maximum_emails_per business export, auto_update_global_blacklist_emails, smtp[0][smtp_id], smtp[0][sender_name], smtp[0][smtp_host], smtp[0][smtp_port], smtp[0][smtp_encryption], smtp[0][smtp_auth], smtp[0][smtp_username], smtp[0][smtp_password], smtp[0][email_signature], smtp[0][maximum_emails_per day], smtp[0][maximum_emails_per hour], smtp[0][delay_between_emails], smtp[0][delay after x_errors]

Note: Change [0] to another number [1] if it's a different SMTP.
EXPORTING LEADS
Get total pages:
POST

https://leadswift.com/api/export_leads_count?api_key=[api_key]

• Params: search_id (required), export_csv_params (required)

Note: To obtain the export_csv_params, follow these steps:

1. Start an export with your desired filters in the UI
2. Monitor the network requests to capture the POST request payload containing the export_csv_params
3. Remove the page and total_pages URL parameters from the payload before using it in the API

The payload will vary depending on your export settings but will look something like this:
Export each page based on total pages:
POST

https://leadswift.com/api/export_leads?api_key=[api_key]

• Params: search_id (required), page (required), total_pages (required), export_csv_params (required)

Note: Call the next page if the response data contains done. When finished, it will return file_name in json format, and you can download it at: https://reports.leadswift.com/export/temp/csv/[file_name].csv
GET CONTACTS OF A LEAD
Get leads:
GET

https://leadswift.com/api/load_contacts?api_key=[api_key]&id=[business_id]-[keyword_id]-[search_id]&page=1&per_page=20

• Params: id, page, per_page, exact_match_domain_only, social_profile, whois, free_provider, q (search keyword),

 

[Fagun Shah]

If webhooks are not available as a trigger then only their team can setup Polling Based trigger for Leadswift.

Polling is a very old way to trigger, webhook is the new norm. Polling also causes more server resource usage for pabbly and trigger app(leadswift in this case).