> ## Documentation Index > Fetch the complete documentation index at: https://usepike.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Remote > Sync Remote employees and contractors into Pike members and contractors, approved time off into capacity, and contractor invoices onto each contractor. The Remote integration syncs the people you employ or contract through Remote into Pike: employees become [members](https://usepike.com/docs/members/overview.md), contractors become Pike contractors, approved time off comes off capacity, and contractor invoices show on each contractor. Resource managers staff projects across countries on real availability, and finance sees what Remote paid each contractor next to the time they logged. ## At a glance | | | | - | - | | **Direction** | Remote to Pike for employments, departments, managers, approved time off and contractor invoices | | **Who sets it up** | Workspace admins, with a Remote API token created by a Remote company owner or admin | | **Plan** | All plans | | **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. | | **Source of truth** | Remote for person fields, employment status, time off and contractor invoices. Pike for capacity, allocations, projects, time and cost rates | ## Before you start You need: * The workspace admin role in Pike. * A Remote user with the company owner or admin role. Only these roles can create a Remote API token. * A Remote API token. In Remote, go to **Company Settings → Integrations & APIs**, open the **Remote API** card, and click **Generate API token**. Name it Pike, accept the terms, and copy the token. Production tokens start with `ra_live_`. * Pike time off types for the Remote time off types you use. You map each type during setup. See [Time off](https://usepike.com/docs/members/time-off.md). * A [work schedule](https://usepike.com/docs/members/working-time.md#work-schedule) or capacity per week for each person in Pike. Remote does not set capacity. ## Connect Remote **1. Open the integration** Go to **Workspace settings → Integrations → Remote** and click **Add integration**. **2. Enter the token** Paste the Remote API token and click **Connect**. Pike checks the token and shows the Remote company name. **3. Map time off types** Under **Time off types**, choose a Pike time off type for each Remote time off type. Pike suggests a mapping from the type names. **4. Choose what syncs** In the **What syncs with Remote** card, turn **Read** on or off for each entity, and choose whether to turn on **Invite new employees**. **5. Import** Click **Import data**. Departments import first, then employments, then time off and contractor invoices. The integration page shows **Connected**, the Remote company name, **Last synced** and **Next sync**. ## What syncs | Remote | Pike | Direction | | - | - | - | | Employments for employees | Members | Remote to Pike | | Employments for contractors | Contractors | Remote to Pike | | Departments | Teams | Remote to Pike | | Managers | Managers | Remote to Pike | | Approved time off | Time off | Remote to Pike | | Contractor invoices | Invoices on the contractor | Remote to Pike | ### Employments | Remote field | Pike field | Notes | | - | - | - | | Full name | Member name | | | Work email | Member email | Also used to match existing members | | Employment type | Employment type | An employee becomes a member. A contractor becomes a Pike contractor with the **Contractor** employment type | | Job title | Position | A position is created when no Pike position has the same name | | Department | Team | A team is created when no Pike team has the same name | | Manager | Manager | When the manager is also a Pike member | | Country | Country | Shown on the member | | Start date | Hire date | | | Status | Member status | An offboarded employment becomes a deactivated member. History is kept | | Employment ID | Remote ID | Shown on the member as the Remote marker | ### Time off | Remote field | Pike field | Notes | | - | - | - | | Employment | Member | | | Time off type | Time off type | Through your type mapping | | Start and end date | Dates | | | Hours per day | Hours per day | A part-day request removes only its hours from capacity | | Status | Not stored | Only requests with the status **Approved** import | Default type mapping: paid time off to Vacation, sick leave to Sick, parental leave to Parental, time off in lieu to Time off in lieu, unpaid leave to Unpaid leave, and every other type to Vacation. Each type counts toward the member's [norm hours](https://usepike.com/docs/members/working-time.md#norm-hours) as set on the Pike type. ### Contractor invoices | Remote field | Pike field | Notes | | - | - | - | | Employment | Contractor | | | Amount and currency | Invoice amount | In the invoice's currency | | Date | Invoice date | | | Status | Status | **Issued**, **In review** or **Paid out** | The contractor's cost rate stays in Pike. Open the contractor to compare invoiced amounts with the cost of their logged time for the same period. See [Cost profile](https://usepike.com/docs/members/cost-profile.md). ## Matching and duplicates On the first import, Pike matches before it creates: * An employment matches a Pike member or contractor with the same work email. A match links the two, and Remote values replace the Pike values for the fields in the mapping. * A department matches a Pike team with the same name. A job title matches a Pike position with the same name. * Time off always imports as new time off. Time off already entered in Pike for the same member and dates stays, and the Remote request is listed in **Sync issues** as an overlap. * Contractor invoices always import as new invoices on the contractor. An employment with no matching member appears under **Unmatched employees** on the integration page. Click **Invite** to send a Pike invite, or **Link to member** to link the employment to a member with a different email. With **Invite new employees** on, Pike sends the invite automatically with the default role the admin chose. ## Which system wins | Entity | Remote owns | Pike owns | | - | - | - | | Members | Name, work email, position, team, manager, country, status, start date | Role, rates, cost profile, work schedule, capacity, project access, allocations | | Contractors | Name, work email, position, status | Cost rate, skills, notes, allocations | | Time off | Dates, hours and type of requests from Remote | Time off requested in Pike | | Contractor invoices | Every field | Nothing. Invoices are read-only in Pike | Edit Remote-owned fields in Remote. Pike shows them as read-only with the Remote marker. ## Sync schedule Pike syncs Remote every 3 hours. On the Enterprise plan, changes sync in real time. **Import data**, **Sync now** and **Refresh** on a member run straight away on every plan. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md). ## Sync settings While Remote is connected, the **What syncs with Remote** card is below the top button row on the integration page. Toggles save immediately. | Entity | Read | Send | | - | - | - | | Employments | Yes | Not available | | Time off | Yes | Not available | | Contractor invoices | Yes | Not available | New connections start with **Read** on for every entity and **Invite new employees** off. ## How it works ```mermaid theme={"system"} sequenceDiagram participant Person as Employee in Remote participant Admin as Admin in Remote participant Remote participant Pike participant RM as Resource manager in Pike Person->>Remote: Request two days of paid time off Admin->>Remote: Approve the request Remote->>Pike: Approved time off, on the next sync or in real time Pike->>Pike: Remove 16 hours from that week's capacity Pike-->>RM: Allocations show the absence RM->>Pike: Move the work to a contractor with free hours ``` ## Use it in Pike ### Plan around approved leave Open **Members → Allocations** to see each person's capacity for the week. Approved Remote time off shows on the day with its type, and the hours are already removed from capacity, so an over-allocated day stands out before the work is due. See [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md). ### Onboard a new hire When an employment becomes active in Remote, the person appears in Pike with their team, position and manager on the next sync. Turn on **Invite new employees**, or click **Invite** under **Unmatched employees**, and the person can log time on their first day. Set their work schedule in Pike so capacity matches their contract. ### Offboard a leaver When an employment is offboarded in Remote, the member is deactivated in Pike. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from their last day. ### Check contractor cost against logged time Open **Members → Contractors** and select a contractor. Their Remote invoices list with amount, date and status next to the hours they logged in Pike. Finance can follow up on a gap between the two before the month closes, not after the margin report is out. ## Deletes and removed records An integration never deletes Pike data. An employment deleted in Remote is marked **Removed in Remote** on the member or contractor, stays in Pike with its history, and stops syncing. A time off request canceled in Remote after approval is removed from Pike capacity on the next sync, and the change appears in the member's time off history. ## Troubleshooting | Symptom | Fix | | - | - | | An employment shows under **Unmatched employees** | The work email in Remote differs from the member's email in Pike. Click **Link to member**, or correct the email in Remote. | | A person's capacity is wrong | Remote does not send working hours. Set the work schedule on the member's contract in Pike. | | Approved time off is missing | Check that **Read** is on for time off and that the request is **Approved** in Remote. Then click **Refresh** on the member. | | Time off shows the wrong type | The Remote type maps to a different Pike type. Change it under **Time off types**. Existing time off updates on the next sync. | | **Sync issues** lists an overlap | Time off for the same dates already exists in Pike. Delete the Pike entry, then click **Retry**. | | **Sync issues** lists an authentication error | The API token was revoked. Generate a new token in Remote and enter it under **Credentials**. | ## Limits * Pike does not write to Remote. Hourly employees submit timesheets in Remote, and contractors create their invoices in Remote. * Remote does not set capacity. Each person's work schedule in Pike does. * Salaries and contract rates stay in Remote. Cost profiles and contractor cost rates are set in Pike. * Contractor invoices are read-only in Pike and do not become project expenses. * Pending, declined or canceled time off requests do not sync. ## Disconnect Go to **Workspace settings → Integrations → Remote** and click **Disconnect**. Syncing stops and every member, contractor, team, time off entry and contractor invoice stays in Pike with its history. Reconnecting the same Remote company relinks the records. ## Related * [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync and sync issues. * [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md): How time off and contracts set available hours. * [Cost profile](https://usepike.com/docs/members/cost-profile.md): Cost rates for members and contractors. * [Deel](https://usepike.com/docs/integrations/deel.md): Contractor rates and timesheets. * [Personio](https://usepike.com/docs/integrations/personio.md): Employees, absences and work schedules. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.