Integration Actions

Key capabilities:

• Trigger pull or push operations per connector, on demand.
• Target data by ID, date range, or other identifier depending on the action.
• Monitor status and progress for every run in one place.
• Cancel in-flight runs and review prior runs for troubleshooting and reconciliation.

How it works

Each connector exposes a set of integration actions appropriate to the platform it connects to. When you run an action, the app creates an action record in Submitted status and notifies the connector. The connector picks up the record, transitions it to Processing, executes the operation, and updates the record to Completed or Failed.

Every action record has:

• An Action Type - what the action does (for example, Pull orders from Shopify by date).
• A Status - where the run is in its lifecycle (Submitted, Processing, Completed, Canceled, Failed).
• A Progress value - a number from 0 to 100 indicating how much of the work has been processed.
• Created and Updated timestamps - when the action was triggered and last changed.
• Action Parameters - the inputs used for the run, such as the date range, external ID, or SKU.

Actions run independently and in parallel, so you can trigger several at once and monitor them side by side.

Where to find integration actions

1. Navigate to Connectors in the app.
2. Select the connector you want to work with.
3. Select the Integration Actions tab.

The list of available actions appears under the Actions dropdown in the top-right of the tab. The table below the filters shows every action that has been triggered for this connector.

Actions by connector type

The actions available depend on the connector category, and the exact set is defined in each connector's manifest. The lists below describe the actions you'll commonly see - open the Actions dropdown on the connector's Integration Actions tab for the authoritative list supported by that connector.

Ecommerce connectors

Ecommerce connectors (such as Shopify, Amazon, BigCommerce, WooCommerce) pull data from the storefront into the app.

Typical actions:

• Pull orders by ID - Retrieves a specific order using its external order ID.
• Pull orders by date - Retrieves all orders created or updated within a date range.
• Pull products by ID - Retrieves a specific product by its external ID.
• Pull products by date - Retrieves products created or updated within a date range.
• Pull products by SKU - Retrieves a specific product using its SKU.
• Pull refunds by date - Retrieves refunds issued within a date range.
• Pull returns by date - Retrieves returns created within a date range.
• Pull returns by extOrder ID - Retrieves returns tied to a specific external order.
• Pull statements by date - Retrieves payout statements within a date range.
• Pull statements transactions - Retrieves transactions associated with a statement.
• Pull locations - Retrieves store or warehouse locations defined in the platform.

ERP connectors

ERP connectors (such as NetSuite, Microsoft Dynamics, Sage Intacct) push transactional data from the app into the ERP and pull back confirmations such as fulfillments and inventory levels.

Typical actions:

• Push orders by ID - Sends a specific order to the ERP.
• Push orders by date - Sends orders created or updated within a date range.
• Push statements - Sends payout statement records to the ERP.
• Push statement transactions - Sends transaction lines tied to statements.
• Pull fulfillments - Retrieves fulfillment records from the ERP.
• Pull inventory - Retrieves inventory counts from the ERP.

Fulfillment connectors

Fulfillment connectors (such as ShipBob, ShipHero, ShipStation, VeraCore, 3PL Central) push orders to the fulfillment provider and pull back shipping and inventory data.

Typical actions:

• Push orders by ID - Sends a specific order to the fulfillment provider.
• Push orders by date - Sends orders created or updated within a date range.
• Pull fulfillments by extOrder ID - Retrieves fulfillment records for a specific external order.
• Pull fulfillments by date - Retrieves fulfillments processed within a date range.
• Pull inventory by SKU - Retrieves on-hand inventory for a specific SKU.
• Pull inventory - Retrieves on-hand inventory across the warehouse.
• Pull locations - Retrieves warehouse locations defined in the provider.
• Pull returns by date - Retrieves return records processed by the provider.

Other connectors

Other connectors include accounting platforms, tax services, EDI, and specialized integrations that don't fit the categories above. Actions vary by platform.

Typical actions:

• Push invoices or Push journal entries - Accounting platforms.
• Pull tax rates - Tax services.
• Push shipments or Pull acknowledgements - EDI partners.
• Pull customers - Customer data platforms.

The integration actions table

The table lists every action run for the connector, newest first.

Default columns

Additional columns

These columns are hidden by default and can be added through column customization:

Column customization options

Select the column customization icon above the table to adjust how columns appear. Available options:

• Show or hide columns - Toggle any default or additional column on or off.
• Reorder columns - Drag columns into the order you want.
• Resize columns - Drag a column's edge to widen or narrow it.
• Pin columns - Lock a column to the left so it stays visible while scrolling.
• Sort - Select a column header to sort ascending or descending.
• Reset to default - Restore the original column set and order.

Your column preferences persist across sessions.

Status values

Table actions

The controls above and within the table let you filter, refresh, and act on action records.

• Status filter - Narrow the list to one or more statuses (Submitted, Processing, Completed, Canceled, Failed).
• Created filter - Limit the list to actions triggered within a date range.
• Advanced filter - Build filters on additional fields such as Action ID, Action Type, Integration, or Updated date.
• Explain filters with Pippen - Use the AI helper to describe the currently applied filters in plain language.
• Refresh - Reload the table to see the latest status and progress.
• Bulk select - Use the checkbox in each row to select multiple actions and cancel them together.
• Row actions - Select a row to open the action's detail view, where you can review parameters and logs. Select Cancel on an in-flight run to stop it.

Running an integration action

1. Navigate to the connector's Integration Actions tab.
2. Select Actions in the top-right to open the list of available actions.
3. Select the action you want to run.
4. Enter any required parameters, such as date range, external ID, or SKU.
5. Select Run to trigger the action.
6. Watch the new row appear in the table with a Submitted status. It transitions to Processing once the connector picks it up, and Progress advances from 0 to 100 as it executes.

Best practices

• Start with a narrow parameter (a single ID or short date range) when testing an action for the first time, then widen the scope once you confirm the result.
• Confirm the ID, SKU, or date range you enter matches an existing record before you run the action. A Completed status with 100% progress means the connector processed the request without error. It does not confirm that any records matched your parameters.
• Use Pull by date actions to backfill after a connector outage or reconnect, rather than pulling all historical data at once.
• Review failed actions in the detail view before triggering a new run. The log output usually points to a data or permission issue that a retry alone won't fix.
• Avoid running overlapping actions with large date ranges on the same connector at the same time. They compete for the same API quota and slow each other down.

Troubleshooting

• An action stays in Submitted for a long time
  The connector has not yet picked up the record. Check that the connector is enabled and healthy on the Connection Details tab. If it remains Submitted for more than a few minutes, contact support.
• An action stays in Processing for a long time
  Large date ranges and connectors with strict API rate limits take longer to complete. Check Progress - if it's still advancing, the run is healthy. If Progress hasn't moved for over an hour, cancel the run and trigger a new one with a smaller parameter.
• An action finishes with a Failed status
  Open the action's detail view and review the log output. Common causes are expired credentials, missing permissions on the external platform, or invalid parameters (for example, an ID that doesn't exist).
• The expected action isn't listed under the Actions dropdown
  Not every connector supports every action. Confirm the action exists for this connector type - ERP connectors don't pull orders, and ecommerce connectors don't push fulfillments. If you believe an action should exist but doesn't, the connector may need a version upgrade.
• Data is pulled or pushed but doesn't appear downstream
  A Completed status means the operation finished on the connector side. If the data isn't appearing where you expect, check downstream routing rules, order routings, and filters that may be excluding the records.
• An action completes with a Completed status, but no data was transferred
  A Completed status with 100% progress confirms the connector executed the request without error. It does not confirm that any records matched the parameters you entered. For example, if you enter an external order ID (extOrderId) when the app expects the Pipe17 order ID, the action can complete with zero records processed. Open the action's detail view and check the record count before assuming the push or pull moved data.

When to escalate

Contact support if:

• An action stays in Submitted for more than a few minutes on a healthy connector.
• An action stays Failed after correcting credentials and parameters.
• You see the same error across multiple connectors, suggesting a platform-side issue.
• An action completes successfully but the record count doesn't match the source system.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the app page.
• Submit a support request with as much relevant detail as possible. Learn how to submit a request.
• For urgent issues, email us directly at support@pipe17.com.

We're here to help you succeed with your operations.