You can use the Float API and Zapier to transfer your Wrike data into Float, enabling seamless automation of your workflows.
Setting up an integration
To set up your Zapier connection, you will need:
Access to the Float Account Owner account.
Wrike account with edit access.
A free “Zaps” Zapier account (a free plan allows Zap creation, but a paid plan is required to run them).
Zapier templates for Wrike and Float
For a quick setup, use Float’s pre-made Zapier templates designed for common workflows between Wrike and Float. View templates for Float-Wrike connection.
💡 Here's a tip: Use a template as a starting point. Once you import the template into your Zapier account, you can add steps or customize the connection as needed.
Creating your own Zaps
Map the corresponding fields
To set up a Zap, you first need to map the corresponding fields between the two systems - for each field that needs to be transferred from Wrike to Float, you need to map the corresponding fields or IDs. For example, if you're transferring an Account from Wrike to a Client in Float, these fields should be mapped accordingly. This mapping ensures data is transferred correctly.
Create the Zap
Once all the fields are mapped, you can create the automation.
Click on the Connect these apps button.
Set up a trigger (Wrike -> Float)
Connect your Wrike account: Follow the prompts to connect your Wrike account to Zapier using your Wrike authentication details.
Configure the Trigger: To create a Zap between Wrike and Float, you must first decide which event you want to use as the trigger for the connection. Triggers act as the starting signal for an automated workflow in Zapier. This may involve specifying filters, time frames, or other criteria for when the Trigger should activate.
Set up the action (Float)
Connect your Float account: Follow the prompts to connect your Float account to Zapier. You will need to sign in as the Account Owner.
Configure the Action: Define the action you want the Zap to take after you trigger your workflow. If a Zapier trigger is the starting signal, then the action is what gets done automatically. This might involve creating a new project or adding tasks in Float based on the information from Wrike.
Test and activate the Zap
After configuring both the Trigger and Action, run a test to ensure the integration works as expected. If the test is successful, you can turn on the Zap to start the integration.
Advanced settings
For more complex integrations, you may need to sync internal IDs between Wrike and Float. You can:
Retrieve IDs via the APIs of both platforms.
Use Zapier’s ‘Test’ step to find field mappings.
Leverage Zapier Tables or custom fields in Wrike to maintain accurate mappings.