Skip to main content

🧩 Integrations

The Integration category in the Workflow editor lets you connect your app to external services and third-party tools—such as Stripe, Zapier, Google Sheets, or Airtable. By attaching these actions to UI elements (e.g., buttons), you can trigger events in other platforms, automate processes, and extend your app’s capabilities beyond its local environment.

1. Stripe Integration​

The Stripe Integration lets you connect your AppStruct app with Stripe, a popular payment processing platform. Once integrated, you can trigger payment actions from UI elements (e.g., buttons), directing users to a Stripe payment link or handling other payment-related tasks. This integration is especially useful for e-commerce apps, subscription services, or any scenario where you need to collect payments seamlessly.

Prerequisites​

  1. Stripe Account:
    • You must have a valid Stripe account. If you don’t have one, sign up at stripe.com.
  2. Payment Link or API Keys:
    • Depending on your use case, you may need a Stripe Payment Link (for a quick checkout) or Stripe API keys (for more advanced functionality).

Setting Up​

  1. Select the UI element (e.g., a Button) that should trigger the payment action.
  2. In the left bar, click Add Action → More actions... to open the workflow canvas.
  3. In the workflow canvas, click the plus (+) icon.
  4. Select Integrations → Stripe.
  5. A Stripe node will appear in the workflow canvas.
  6. Click on this node to open the Stripe settings panel.
  7. Enter the URL to a Stripe payment link. For example, if you created a one-time or subscription link in your Stripe dashboard, copy and paste it here.
  8. When users click the button, they’ll be redirected to this link to complete their payment.

Testing​

  1. After entering your Stripe payment link (or other details), click Save.
  2. Click Preview at the top-right corner of the AppStruct editor.
  3. Interact with the button or element you configured to see if it correctly redirects to Stripe’s payment page.
  4. If you have test mode enabled in Stripe, you can run a test transaction to confirm the workflow is successful.

Best Practices​

  • Use Stripe Test Mode: Before going live, enable test mode in your Stripe dashboard to verify the payment flow without charging real cards.
  • Ensure Secure Links: Only use HTTPS links from Stripe to maintain secure transactions.
  • Clear Call-to-Action: Label your payment button clearly (e.g., “Pay Now,” “Buy,” or “Donate”) so users understand they’re initiating a payment.
  • Keep Stripe Documentation Handy: For advanced use cases (e.g., subscription management, webhooks), consult Stripe’s documentation.

2. Zapier​

Integrating Zapier with AppStruct allows you to create automated workflows (Zaps) that connect your app with external applications. Once set up, you can trigger actions in your app based on events in other services, or vice versa. This feature is ideal for automating tasks such as sending notifications, updating records, or syncing data between platforms.

Setting Up​

  1. Navigate to the Integrations section. Look for the Zapier integration option, which is marked with the Zapier logo.
  2. Select the Zapier integration and you will be transferred to Zapier Interface.
  3. Once connected, save your settings. Your AppStruct project is now ready to receive and send data via Zapier.

Note on Selecting Pairing Apps:​

When you reach the step in Zapier where you choose which app to connect with AppStruct:

  • Click on the search bar to open a search field.
  • Type the name of the service you want to pair with (e.g., Gmail) to see available options.
  • You may also see a list of apps displayed underneath.
  • Clicking on one of these apps will take you to a dedicated page with detailed instructions on how to connect AppStruct to that specific service.

Supported Triggers & Actions​

Triggers (Events That Start a Zap):

  1. New Row
    • Trigger: Fires when a new row is created in the specified table.
    • Use Case: Automatically send notifications or update another system whenever a new record is added (e.g., new user sign-up, new order).
  2. New Table
    • Trigger: Fires when a new table is created in the specified project.
    • Use Case: Kick off a workflow whenever you add a new data structure to your AppStruct project (e.g., notify your team or set up default columns).

Actions (Operations Performed in AppStruct)

  1. Create Table
    • Action: Creates a new table in the specified project.
    • Use Case: Programmatically generate tables from external triggers (e.g., when a new campaign starts, automatically create a campaign-specific table).
  2. Insert Record
    • Action: Adds a new row to the specified table.
    • Use Case: Sync data from other apps or forms into AppStruct (e.g., insert new customer information from a CRM).
  3. Get Table Data
    • Action: Retrieves data from a specified table.
    • Use Case: Use AppStruct data in other apps or processes (e.g., fetch a list of products for an email campaign).
  4. Add Column
    • Action: Adds a column to an existing table.
    • Use Case: Expand the data structure in AppStruct based on external triggers.
  5. Delete Record
    • Action: Removes a row from the specified table by ID.
    • Use Case: Keep AppStruct data clean by automatically deleting entries when they’re removed from another system (e.g., canceled orders).
  6. Update Record
    • Action: Updates a row in the specified table by ID.
    • Use Case: Keep data in sync between AppStruct and other platforms (e.g., update a user’s profile information after changes in a CRM).

How These Triggers & Actions Work Together​

  1. New Row → Insert Record
    • When a new row is added in one table, automatically insert a corresponding record in another table or system.
    • Example: A new order in your e-commerce system creates a corresponding record in an AppStruct table.
  2. New Table → Add Column
    • Upon creating a new table in AppStruct, automatically add predefined columns to set up your data structure.
    • Example: Each time you start a new project, add default columns like “Status” or “Owner.”
  3. Get Table Data → Update Record
    • Fetch existing data from AppStruct, transform it, and then update specific records.
    • Example: Retrieve a list of customers, filter them in Zapier, and update those who meet certain criteria (e.g., mark as “VIP”).

Best Practices​

  • Plan Your Workflow: Before setting up the integration, outline the events and actions you need to automate. This ensures your Zaps are efficient and only trigger when necessary.
  • Test Thoroughly: Use Zapier’s test feature to simulate triggers and actions. Verify that the data received by AppStruct is accurate and complete.
  • Document Your Zaps: Maintain documentation for each Zap you create. This helps in troubleshooting and future updates.
  • Stay Updated: Check both AppStruct and Zapier documentation regularly for new features and best practices to enhance your workflows.

Need Assistance?​

If you encounter any challenges or require further guidance while building your app, please refer to the Documentation or, contact our support team at [email protected].