This article explains what to expect when setting up an integration with Appical, from request to go-live.

The process at a glance:

Important: the timeline guideline only starts counting once two things are confirmed: access to your data, and a completed mapping document. Delays in either of these will naturally push back the start date, and are not counted against the estimate.

Response time: the Integration team aims to respond to emails within 48 hours, though this can vary depending on volume and complexity.

What affects your timeline the most: the biggest factor in keeping your integration on schedule is how quickly information and confirmations are provided on your side, for example system access details, mapping decisions, and simulation feedback. To help keep things moving:

If we don't hear from you: if Appical does not receive a response to a request for an extended period, we will follow up periodically. If there is still no response after several follow-ups, we will send a final notice explaining that the ticket will be closed if no response is received. If this happens and you want to continue later, a new request will need to be submitted, which places it at the start of the queue again. If you know in advance that you'll need more time, just let your Appical contact know — we can place the request on hold for an agreed period instead.

This section describes each phase in more technical detail.

1. Request integration. Submitted through your Implementation Consultant or CSM. See Making a Request for an Integration for the information needed at this stage.

2. Review and agree type. Appical determines whether the integration meets the standard criteria (see Standard vs Custom Integrations). It is helpful if the person scoping the integration has visibility into both the HR process and the technical structure of the source system, since requirements sometimes expand once the technical possibilities become clear (for example, discovering that manager data sits in a separate endpoint).

3. Complete mapping. Appical and your team agree the mapping document (see The Mapping Document Explained), which covers data access, business rules, data mapping, and conditional mapping (for example, tag and group assignment logic). The timeline for development does not start until this document is complete and data access is confirmed.

4. Development. The integration is built according to the confirmed mapping. Standard integrations reuse existing, proven configuration logic in Appical's middleware, which is generally faster than building custom logic from scratch. Custom integrations may require changes to the middleware configuration or, in some cases, to the Appical API.

5. Simulation. This is your team's opportunity to verify data mapping, timing, and processing logic before go-live, using realistic test scenarios, including edge cases such as manager reassignment or account archiving.

6. Go-live. Once simulation is confirmed successful, the integration is activated and runs on the agreed schedule (typically once per day).

Non-responsiveness process (technical detail): if a request is outstanding, Appical sends periodic follow-up requests. After multiple follow-ups over several weeks with no response, a final notice is sent stating that the ticket will be closed without further action. Reopening after closure requires a new request, which re-enters the queue rather than resuming from its prior position. If a delay is expected, the ticket can instead be placed on hold for an agreed period — contact your Appical representative in advance to arrange this.

👉 Let us know if this article answered your question by using the buttons below. If not, get in touch with our Support Channel for more information.