AtomPark Software

How to integrate AtomPark Software with Webflow

Automate email campaigns and SMS notifications based on site activity without manual data transfer with AtomPark. Connect form submissions to email verification services, trigger campaigns when you publish CMS content, or send transactional SMS for order confirmations and event reminders.

You can integrate AtomPark Software with Webflow through custom API integration using the Webflow REST API and AtomPark SMS API v3. This enables you to build middleware that captures form submissions for email campaigns, triggers campaigns from Webflow CMS events, or sends SMS notifications for site events.

Note: AtomPark is an SMS gateway and email marketing platform, not a CMS, so it cannot participate in CMS content synchronization.

Build with Webflow and AtomPark Software (Custom Integration)

API integration gives you direct control over data exchange between platforms. Build middleware (server-side code that processes and routes data between systems) that receives Webflow events through webhooks or polls the REST API, transforms the data, and forwards it to AtomPark's email or SMS endpoints.

Use this method when you need real-time synchronization, custom validation rules, or workflows that combine multiple API calls. Implement OAuth 2.0 authentication for Webflow, MD5 checksum authentication for AtomPark, rate limit monitoring, and error recovery logic.

Critical technical constraints apply. Webflow enforces strict plan-based rate limits (60-120 requests/minute depending on plan). AtomPark's rate limits are undocumented, which creates production risk.

Contact AtomPark support to obtain specific rate limit information before deploying to production. Webflow uses modern OAuth 2.0 authentication while AtomPark uses legacy MD5 checksums, requiring careful security implementation in your middleware layer.

Form submission quotas also apply based on your Webflow plan. Basic plans include 100 submissions per month, CMS plans include 500 submissions per month, and Business plans include 2,000 submissions per month. Overages cost $1 per 100 submissions. Account for these quota restrictions in your integration design.

Capture form submissions for email campaigns

Webflow form submissions provide structured contact data that you can route to AtomPark for email verification and campaign management. Use the Webflow Forms API to retrieve submission data, verify emails through AtomPark's validation service, and add contacts to targeted mailing lists.

Your integration uses Webflow webhooks or polling to monitor form submissions. Extract email addresses, phone numbers, and custom fields. Send this data to AtomPark's email or SMS APIs for list management and campaign execution.

The integration supports these capabilities:

• List form submissions with GET /v2/sites/{siteid}/forms/{formid}/submissions to retrieve contact data
• Verify email addresses using AtomPark's email verification service to maintain list hygiene
• Add contacts to mailing lists through AtomPark's bulk email API for campaign management
• Send transactional SMS for immediate notifications

Technical constraints apply. Webflow forms support a maximum of 100 fields per form. The platform provides Plain, Email, Phone, and Number field types. Plan-based submission limits restrict your monthly quota as detailed above.

Trigger campaigns from Webflow CMS events

Webflow webhooks trigger automated workflows when you publish new content. When you publish blog posts, product listings, or portfolio items, webhook events fire. Your middleware receives these events and formats them for use with email or SMS platforms.

Set up webhooks through the Webflow webhooks system. Receive real-time notifications for collection item changes. Your integration transforms CMS field data into email content or subscriber list updates that AtomPark processes. Monitor Webflow's five webhook events including collection_item_created, collection_item_changed, collection_item_deleted, collection_item_unpublished, and site_publish.

Monitor these webhook events:

• collectionitemcreated for new CMS items that trigger campaign creation or subscriber notifications
• collectionitemchanged for content updates that generate follow-up campaigns
• collectionitemdeleted for removed items that trigger list cleanup or archive notifications
• collectionitemunpublished for published items made draft that trigger status updates
• site_publish for site-wide publishes that trigger full campaign synchronization

Implementation follows this pattern. Register webhooks using POST /v2/sites/{site_id}/webhooks. Include your endpoint URL and chosen trigger type. Webflow sends POST requests to your endpoint containing collection item data in JSON format. Validate the request using the webhook signature as explained in working with webhooks. Forward formatted data to AtomPark's SMS or email APIs.

Send SMS notifications for site events

AtomPark's Atomic SMS Sender enables transactional SMS messaging with scheduled sending, personalization, and worldwide delivery to 200+ countries. Trigger SMS notifications for site events through custom API integration.

API integration supports these patterns:

• Form submission alerts
• Order confirmations
• Event reminders
• Time-sensitive promotions

Per Webflow's webhook system, site events can trigger webhooks. Your middleware forwards data to AtomPark's SMS API for delivery.

AtomPark's SMS gateway sends transactional messages triggered by Webflow activity. Your integration receives webhook notifications or polls the API for specific events.

This pattern works for order confirmations, appointment reminders, or urgent alerts where SMS provides better reach than email. Extract phone numbers from form submissions or CMS fields.

Format messages according to SMS length constraints (160 GSM-7 or 70 UCS-2 characters per segment, or 67 characters for Unicode segments). Submit batch requests to AtomPark's SMS endpoint (maximum 1,000 recipients per batch or 500 per group, verify current limits with AtomPark).

SMS specifications apply. Messages use 160 characters for GSM-7 encoding and 70 characters for UCS-2 (Unicode) encoding per segment. Longer messages split across multiple segments with reduced character counts (67 characters per segment for Unicode). AtomPark's API accepts UTF-8 encoding and supports personalization variables for recipient-specific content.

Authentication and security requirements matter. Webflow uses OAuth 2.0 with Bearer tokens as detailed in the authentication documentation. Format requests with Authorization: Bearer {your_token} headers. Tokens expire after 365 days of inactivity, requiring regeneration. AtomPark uses public/private key pairs with MD5 checksums. MD5 is cryptographically broken and no longer secure.

While HTTPS protects transmission, consider requesting modern authentication methods from AtomPark for production deployments. AtomPark recommends POST requests to prevent credentials appearing in proxy logs when implementing this authentication method.

Store credentials in environment variables rather than committing them to source code. Implement token rotation procedures, particularly for Webflow bearer tokens which expire after 365 days of inactivity. Revoke compromised credentials immediately through each platform's security settings.

What you can build

Build these workflows by connecting Webflow events to AtomPark's email and SMS APIs:

• Lead qualification system: Capture prospect information through Webflow forms and filter invalid contacts using custom API integration with AtomPark's email verification service, then route qualified leads to targeted email nurture campaigns through AtomPark's bulk email service based on form responses
• Content distribution automation: Publish blog posts or resource library content in Webflow CMS and trigger webhook notifications that generate subscriber email campaigns through AtomPark via custom API integration, including automatic excerpt formatting and scheduling for ideal send times
• Multi-channel event registration: Collect attendee details through event landing page registration forms and send immediate confirmation emails through AtomPark's bulk email sender, then deliver SMS reminders with event details using AtomPark's SMS gateway (scheduled SMS delivery requires custom API integration with task queue such as AWS Lambda or cron job to handle 24-hour delays)
• E-commerce cart recovery: Store product catalog in Webflow CMS and route abandoned cart data to AtomPark via custom API integration for automated email sequences with personalized product recommendations, combined with SMS alerts for limited-time discounts (requires external cart tracking system such as Shopify, WooCommerce integration, or custom backend as Webflow CMS does not natively track cart abandonment)