FAQ

There are 4 options for Webhooks in DataBlend:

• Two specific webhook implementations because they don't match industry standard ones: Hubspot and Intacct.
• The other two options, Standard and Simple, should support >99% of all other systems that can send webhooks.

The main use case for webhooks is to add data to DataBlend when an event occurs in an external system. Events typically mean they should be added to a real time stream since there's no "collection" or boundary for events. The stream can then be processed on a recurring schedule that queries the stream for events that have not yet been "processed", typically a date. 

We have investigated this but have constraints due to the nature of connectors. In our current architecture, credentials must be created before they can be associated with a collector or data target, data sources and schemas need to be created before creating a query, collectors and data targets have to be created before adding to a workflow. We also have some security concerns .e.g. How would sensitive data be deployed to another group/environment? How would queries be deployed when they reference schemas in other groups?

We are planning to revisit this and investigate options that may be made available only to implementers (Datablend + Partners) vs end users but unfortunately don’t have anymore details available to share.

For most users, templates are limited to be used in one group. Some Internal DataBlend users are granted the ability to create public templates that are available to all groups. Cross-group templates are difficult due to similar reasons described above.

Primary rationale for not supporting this is risk of easily creating an infinite loop of workflows e.g, Workflow A kicks off Workflow B which kicks off Workflow A again (also deeper where it gets to Workflow Z). However, there is a workaround that can be implemented using tools.
Linking Two Workflows Together

This message is being returned directly by Sage Intacct. It means Sage Intacct is temporarily throttling API traffic because too many requests were submitted in a short period of time. Sage identifies this as a 429 / GW-0010 error, which occurs when an API client reaches its assigned rate limit.

This is not a data validation or mapping issue within DataBlend. DataBlend is making API calls to Sage Intacct using Sage-supported API methods, but Sage controls the rate limits and throttling behavior on the Intacct side.

We recommend reviewing API activity within Sage Intacct to determine whether other connected applications or scheduled processes are contributing to the limit. In particular, please check whether any other integrations, reporting tools, custom scripts, AP/expense platforms, CRM connections, or BI/data warehouse tools are using the same Intacct company or shared Web Services credentials. It would also be helpful to confirm whether any other jobs are running at or near the same time as the DataBlend workflow.

Sage also indicates that throttle limits are tied to the customer’s contracted level of service, so if total API usage across all systems has increased, Sage may need to review whether the current API entitlement is sufficient.

At this point, the next step would be to engage Sage Intacct Support to review the API activity associated with your environment and determine what processes or integrations may be contributing to the throttle limit. Once additional information is available from Sage, we would be happy to review the findings and provide any guidance we can regarding the DataBlend workflow.