Home Manuals

Manuals

By Alex Mishyn
14 articles

AI Variables: Creation and Usage

AI Variables are variables that allow you to use artificial intelligence to adjust static values. For example, they can automatically translate names from Latin to Cyrillic, remove prefixes such as “LLC” from company names, and more. *By default, all users have an AI token from Grinfi enabled (with a limit of 1,000 requests per month). Users can connect their own LLM token - in this case, there will be no limits or restrictions on the number of requests on the Grinfi side. Instructions on how to connect your own LLM are available at this link. Default AI Variables In the AI Variables section, there are three predefined AI variables designed to clean and normalize values (e.g., removing emojis, pronouns, academic degrees, adjusting formatting, etc.): - ai_contact_first_name - cleans and formats the contact’s first name ​*(example: “MR JOHN” → “John”)* - ai_company_conversational - formats the company name ​*(example: “GRINFI LLC” → “Grinfi”)* - ai_position_conversational - formats the job title ​*(example: “Senior Certified Accountant” → “Accountant”)* How to create an AI Variable On the sidebar, go to the AI Variable section, then click Add Variable. ​ In the modal window: - Enter the Variable name (1) – the identifier you will use later. - Select the LLM (2) and the required Model version (3). - In the Prompt field (4), select the variable value you want to modify and write a detailed instruction (prompt) for the AI specifying what needs to be done. - Enable the Fallback switch (5) and enter text or select a variable to be used when the AI cannot generate a result. - On the right side of the window, select a Contact (6) to test and generate a preview of the result (7). - Click Create (8) to save the variable. In the advanced LLM model settings, you can configure the following parameters: - Use Preset (1) - defines the tone of generation: accurate / creative / balanced. - Max Tokens (2) - specifies the maximum number of tokens the model can use to generate a result. If the output is truncated or incomplete, try increasing this value. - Reasoning Effort (3) - limits the amount of computational resources the model uses for reasoning (applies to reasoning models). Available values: minimal, low, medium, high. Lowering this parameter allows for faster responses and fewer tokens used, but may reduce the depth of analysis. - Verbosity (4) - defines the level of detail in the model’s response. Available values: low, medium, high. Lower values produce more concise responses, while higher values make them more detailed and descriptive. ​ Using AI Variables AI Variables can be used in any nodes that support variables - such as sending connection requests, messages, or commenting on posts. To apply an AI variable in a node, click Insert Variables, then select the AI Variable section. ​

Last updated on Jul 02, 2026

AI Templates: Creation and Usage

With AI Templates, you can easily generate messages texts directly inside the platform using configurable AI modules. How to create an AI Template? In the sidebar, find the AI Templates section and click Create. In the modal window, enter a template name and select its usage type: personal message/ email/ InMail message/ connection request. If needed, share the template with colleagues in your workspace and click Create. ​ In the text field, you can add a static part of the message that will not be generated by AI (1). After adding an AI Block (2) inside the editor (3), specify the contextual information for the AI - what exactly needs to be generated. ​ *By default, all users have an AI token from Grinfi enabled (with a limit of 1,000 requests per month). Users can connect their own LLM token - in this case, there will be no limits or restrictions on the number of requests on the Grinfi side. Instructions on how to connect your own LLM are available at this link. ​ Scroll down and select which LLM (1) to use for generation, choose the required model (2), and provide a detailed instruction (prompt) (3) for the AI (for example: message length, writing style, core offer details, variables to use as data sources for generation, etc.). ​ Enable the Enable Fallback Message toggle (4) and define the text that will be used in cases where the AI fails to generate a result based on the prompt. On the right side of the window, you can select a relevant contact (5) and generate a preview result based on it for testing (6). If the template meets your requirements, click Create AI Example (7) to add it to AI Message Examples (8). Based on the saved examples, the AI will be able to generate and validate results for your requests more accurately. Using AI Templates Created templates can be used in automations within the relevant nodes that include text fields: messages, comments, emails, and more. To apply a template, enable the Use Template toggle in the selected node and choose the required template from AI Templates. ​

Last updated on Jul 02, 2026

Advanced Enrichment: How to Use

The Advanced Enrichment node in the Grinfi automation builder is a tool for the on-demand update and actualization of contact data using information directly from LinkedIn. It ensures that before executing a critical step (such as generating a personalized message), the system finds and utilizes the most up-to-date information about the contact. ⚠️ Important: Feature Availability and Pricing The Advanced Enrichment feature is available exclusively in the new subscription formats introduced on April 28, 2026. If you purchased your subscription before this date and have not switched to a new plan, this functionality will be unavailable. To gain access, you need to upgrade your subscription. - View new pricing plans - Go to the billing management page 🟡 Note: The Advanced Enrichment node is billed using internal credits. Each successful enrichment consumes 1 credit from your balance (the number of credits depends on your current subscription plan). If you run out of credits, the node will stop functioning. How Default Data Enrichment Works To better understand the value of this node, it is important to know how the platform processes data by default when importing contacts: 1. When a new contact is uploaded to Grinfi, the platform automatically checks whether it already exists in the internal database. 2. Instant data retrieval: If the contact is found and its last enrichment occurred less than 3 months ago, the information is instantly pulled from the database. 3. Re-enrichment: If the contact is found but its data hasn't been updated for more than 3 months, the system places it in a queue for a new enrichment to refresh the info. 4. If the contact is entirely new and not in the database, it is placed in the enrichment queue. 5. Depending on the load and queue size, the actual enrichment process (not from the database) can take from a few hours to several days. The Advanced Enrichment function is designed specifically to eliminate the possibility of using potentially outdated data. It forces the system to ignore the database and update information directly while the automation is running. Advanced Enrichment Node Configuration In the node configuration menu, two operating modes are available: ​ Enrich all contacts (1): If this checkbox is selected, the system will force the enrichment process for every contact that reaches this node, regardless of when their data was last updated. This guarantees 100% data relevance but consumes the most credits. Filter by last enrichment date (2): A smart mode that allows you to update only outdated profiles, helping you save credits. - In the Only enrich if older than (3) dropdown list, set a time limit for the last update. - If a contact was enriched more recently than the specified timeframe, the system will pass them through, assigning a Skipped status to the node. If the data is older, the contact will be sent for priority enrichment. ⚠️ Note: If a contact is sent for an update via the Advanced Enrichment node, its progress through the automation will be temporarily paused. The contact will remain at this node until the data collection is fully completed, and only then will it proceed to the next step of your automation.

Last updated on Jul 02, 2026

Webhook and API Call Setup

The Webhook Call and API Call features allow you to seamlessly export data about contacts or companies to external resources at any stage of the automation. Setting up a Webhook Call Step 1: Create a Webhook in Settings Сreate a webhook and choose the type based on the data you plan to export: - Contact Export (Custom Call) - use this to transmit data about individual contacts. - Account Export (Custom Call) - use this to transmit data about companies (accounts). For a detailed guide on creating webhooks, refer to this article: How to Create a Webhook. Step 2: Add the Webhook to the Automation Go to the automation builder and add an Call Custom Webhook node at the required point in your sequence, then select the webhook in the node settings. Setting up an API Call This section covers connecting to an external API and sending automated requests with dynamic data (variables). ​ Stage 1: Configure API Call Accounts Create your authorization credentials. - Navigate to API Call Accounts in the settings section (1). - Click Add API call account (2). - In the modal window, fill in: - Connection name (3): enter a name for this connection. - Auth type (4): choose the method required by your service and enter the required data: There are 3 Auth types: | Auth Type | Required Data | | --- | --- | | API Key | Key name, Value, Add to | | Bearer token | Token | | Basic auth | Username, Password | - Click Create (5). Stage 2: Adding the API Call to the Sequence 1. Open the automation builder. 2. Add the API Call node at the desired point in your workflow. Stage 3: API Call Settings 1. Basic Configuration - API call (headers) account (1): Select your saved authorization profile. - Method (2): Choose the HTTP method. - Endpoint (3): Enter the external API URL. Use the { } Insert variables (4) button to include dynamic data. - Test API Call (5): Test the API Call setup. ​ 2. Data Transmission (Optional) - Body (1): If you are using POST, PUT, or PATCH methods, you can define the request body here. - Query parameters (2): Query string parameters, provided as Key/Value pairs. - Headers (3): Add any additional HTTP headers required. ​ 3. Advanced Settings At the bottom of the panel find important stability settings: - Timeout (1): Server response wait time (default is 30s). - Auto retry on errors (2): Enable this checkbox to allow the system to automatically retry the request in case of temporary failures (network errors, rate limits, or 5xx server errors). - Remove Empty Values (3): Enable this option to automatically exclude empty, null, or undefined values from the request. This helps protect your data from being accidentally overwritten with empty strings.

Last updated on Jul 02, 2026

Contact Distribution Across Sender Profiles and Restart Options in Automation

At the stage of selecting sender profiles during automation setup, you can choose the method for distributing contacts across the sender profiles. ​ To do this, you need to select the desired number of sender profiles to be involved in the automation and set the distribution method: 1. Rotate to a new Sender profile – the contact will be assigned to a profile that hasn't interacted with them before. The system will go through all sender profiles and choose the one that hasn’t had any previous engagement with these leads — essentially starting everything from scratch (e.g., sending a connection request, etc.). 2. Prioritize Profiles with prior engagement – the contact will be assigned to the profile that has previously interacted with them. So, if there was prior engagement (a message or email was sent), the system will continue the automation from that same sender profile. This is useful when you've already started a campaign and now want to simply continue it. 3. Fair Balance Rotation – the system will evenly distribute leads between sender profiles — starting randomly but taking the total number of leads into account. For example, if you have 10 sender profiles and you add 2 more, new leads will be assigned to these two until the number of leads is balanced across all profiles. *this is the default option. 4. Random Rotation – contacts are assigned randomly across sender profiles with no balancing applied. This might be helpful in some scenarios, especially if you have multiple segments — in this case, the system will distribute completely at random. With these distribution options, you can now easily restart contacts from the beginning, from any node in the automation. When restarting leads, you can choose to launch them again from the same sender and segment, but the new automation settings will be applied. Restart Option The Automation Builder allows you to select one or more contacts at any node and restart the task for them using one of the following options: 1. Cancel – stops further automation for the selected contacts at the current stage. 2. Skip – skips the current step and immediately moves the contact to the next one. 3. Restart on this Node – restarts the contact from the current node (useful when the contact has a Failed or Cancelled status). 4. Restart from Top – cancels the current task and sends the contact back to the beginning of the automation. ​ To access the restart menu, locate the desired node(step) and status, then click the number next to that status. A modal window will open, where you can select the required contacts and either restart them or cancel a specific task. ​ Important Notes: - The restart function is only available for contacts with the following statuses: in progress, failed, or cancelled. - Contacts with the status done, skipped cannot be restarted. - For contacts that have finished the automation, the restart function is only available with the restart from top option. - It is not possible to restart contacts from the Segment node (the default node in every automation, marked as node #1).

Last updated on Jul 02, 2026

Manual Tasks: How to Create?

What does the Manual Tasks feature include? Manual tasks allow you to systematically create reminders about the need to interact with a contact. The settings let you prepare a template in advance for each type of task, but they are not executed automatically. The user must perform the action manually and then confirm its completion in the corresponding section. ​ Available Task types: - Send connection request - Send direct message - Visit profile - Endorse skills - Like the latest post - Comment the latest post - Withdraw connection request - Send email ​ *Important: Manual Tasks serve exclusively as a planning tool - the functionality does not support delayed execution, as it is implemented, for example, in Telegram. The user must manually perform the action specified in the task and then confirm its completion in the corresponding section. It’s not possible to confirm a task in advance. It is considered completed only at the moment of actual confirmation, regardless of the previously set date. The specified date serves merely as a reference point for the user who will perform the task. ​ Creating a Manual Task To create a task, open the contact card and go to the "Tasks" section on the top panel. Then click "Create Task" and select the task type. ​ Let’s walk through the creation process using the example of sending a message. 1. Sender Profile - choose the sender profile that will perform the task. 2. Task Assignee - the user responsible for executing the task (this user will later confirm the task execution). 3. Date Execution - set the date for task execution. 4. Time - set the time of execution. 5. Message - a field for creating a message template; you can also attach files or add variables if needed. 6. Note – an optional field for leaving a note to the responsible user. To complete the task creation, click Confirm. Task Manager and Task confirmation You can find the Task Manager in the sidebar menu. The section allows sorting tasks by: - Your own tasks or the tasks of all team members(1) - Task status(2) - Date (3) Advanced filters: task type, contact, automation, sender profile, and assignee (4) By clicking on a specific task, you can view its details, modify the template if needed, or reschedule the time. After reviewing and selecting the relevant tasks, four types of actions become available for them: 1. Run in Bulk - tasks matching the set criteria are displayed one by one for execution. 2. Complete - mark a task as completed without actually performing it. ​*The function only creates a record of the task completion - the user must perform the action manually (send a message, send a connection request, etc.). 3. Change Assignee - assign the task to a different user responsible for its completion. 4. Cancel - cancel the task.

Last updated on Jul 02, 2026

InMails: How the Feature Works

Limits and Credits for InMails InMails are personal messages that can be sent to any LinkedIn user, even if you are not directly connected. LinkedIn guarantees that the message will be delivered and opened. Otherwise, the spent credit will be returned to you. These messages can be sent only from the Sales Navigator Premium plan. InMail is also available from free profiles and other premium plans, but only if the recipient has the Open Profile feature enabled. ​ The number of available InMails per month depends on the subscription type: | LinkedIn Subscription Type | Number of InMails per Month | | --- | --- | | Premium Career | ~ 5 credits | | Premium Business | ~ 15 credits | | Sales Navigator | ~ 50 credits (unused credits roll over, up to ~ 150) | | Recruiter Lite | ~ 30 credits | | Basic (free) | ~ 5–15, and only to recipients with "Open Profile" | *The platform works most reliably with accounts that have a Sales Navigator subscription. How to Send an InMail via Grinfi 1. Through Automation Open the Automation Builder => click “+” and select “Send InMail” Fill in the Subject (1) and the Message body (2). You can use variables (3) or attach files (4). ​ Click Create, and all contacts that pass through this automation step will receive the InMail. ​ Tip: ​**Plan your automation to minimize credit usage while maximizing efficiency. For example, send InMails only to those contacts who haven’t accepted your connection request within a certain time.* ​ ** If your profile does not have a Premium plan, use Condition Rules: set a rule that the recipient must have Open Profile enabled, and apply the Send InMail step only along the “Rule #1” branch. Otherwise, once credits run out, all remaining contacts in the queue will receive the status Failed. 2. Through Messenger Go to Messenger => open the conversation with the contact you want to reach => select the Sender profile (1) and the InMail channel (2). Write the subject and message text, then click Send. Common Errors When Sending InMails & How to Fix Them - “You do not have enough InMail credits” – you’ve run out of InMail credits under your current plan. Wait until the next billing cycle or upgrade your subscription if you need more. - “Awaiting reply: new InMail can be sent only after the contact replied” – this contact has already received an InMail and hasn’t replied yet. Without Sales Navigator, you must wait for their reply before sending another InMail. With Sales Navigator, you can send more, provided you have available credits. - “I can see the reply in Sales Navigator but not in Grinfi” – the message hasn’t yet synced with the platform. While Messenger syncs instantly, InMails sync approximately every 2 hours. Please wait.

Last updated on Jul 02, 2026

Messenger Features

On the left sidebar, open the “Messages” section to access a unified space with all conversations from every connected sender profile at once. Alternatively, you can switch to a specific profile if needed (1). At the top of the main page, there are 2 sections: - Inbox - here you’ll see conversations after a contact has replied to your message. - Outbox - displays all outgoing conversations. Above the conversations, there are pipeline stages(2). Each conversation shows indicators for unread messages (3) and automation pauses (4). You can filter conversations by: 1. Automation name 2. List where the contact is stored 3. Assigned tag 4. Communication channel 5. Last message (inbox or outbox) 6. Unread messages 7. Status: “Automation paused after reply” Additionally, you can hide sender profiles that are not involved in automation. When you open a conversation, you’ll see the full chronological history of all interactions with that contact. If you’re working across LinkedIn and Email at the same time, messages from both channels will appear in order of receipt. In the message input window, you can select the sender profile (1) to send from, choose the channel (2) (Email, LinkedIn, or InMail), and attach a file (3). You can also highlight any part of your text to activate the “ask AI” feature, which allows you to get AI assistance, for example, to shorten or rewrite your draft. If you need to reply to a contact within the same email thread instead of starting a new one, scroll up to the desired message and click “Reply.” The subject line and previous thread will load automatically. Start typing your reply directly under the subject line. *Do not delete or modify the pre-loaded history - it serves as a log to ensure your reply goes into the correct thread. This formatting is required by external email providers. Once the message is sent, the log will be hidden, and the recipient will see a clean, properly formatted email. The right panel contains detailed contact information: - Full name - Job title - LinkedIn profile link - Email address - Phone number - Location and workplace Below the contact’s name, you’ll find a “Unpause Automations” button, which allows you to continue the sequence if, for example, their reply does not require manual handling. Clicking the three dots next to the contact’s name allows you to: - add/remove them from automation; - mark messages as unread; - export via webhook; - add to stop-list; - delete the contact. Further down, you’ll also see: - current stage in the pipeline; - list the contact belongs to; - tag management block; - values of custom variables (if assigned). Also, you'll find additional tabs in an active conversation: - Overview - all contact information imported into Grinfi. - Activity - full interaction history. - Notes - add and store notes for the contact. - Tasks - track automatic actions + create manual tasks for the contact (outside automation rules or after automation is complete). Manual tasks require additional user confirmation before execution. Confirmation happens in the Tasks section on the left sidebar, where all manual tasks are listed. For more details about manual tasks, take a look at the dedicated guide.

Last updated on Jul 02, 2026

Adding contacts to the automation

After connecting sender profiles, importing contacts, and creating your automation, the next step is adding contacts to the automation to begin operating. There are several ways to do this: - During the automation setup stage Once you have created a sequence and added the required number of sender profiles, the next step is to add contacts either directly from the CRM or through imports. You can find more details in this article. The following methods apply to automations that have already been created: - Manual addition within the automation Above each segment, you’ll find the “Add contacts” button. Clicking it opens a window with a list of contacts and available filters. Use the filters to find the right contacts and add them to the automation. You can add contacts separately for each segment and at any time. - #### Auto filter Another method is to set an auto filter at the segment level. This feature automatically adds contacts to the campaign based on specified criteria. As soon as a contact matching the filter conditions appears in the CRM, it will be immediately added to the automation. - #### Adding via the CRM In the CRM section, filter your contacts according to your needs => select all or a specific number => click “Send to automation” and choose the desired automation. Note: When using this method, contacts will only be added to #1 Segment. So if you have multiple segments, this method may not be suitable.

Last updated on Jul 02, 2026

Automation Overview: Key Functions

On the left sidebar, go to the "Automations" section and click "Create New Automation". In the modal window, you’ll have two options: - Use one of the ready-made templates (1). - Build automation from scratch (2). Among the suggested templates, you can find frameworks of automations for different purposes. If none of them fit, you can create your own by clicking Build manually. ​ Then, you will be redirected to the automation builder, which consists of 4 stages: ​ 1. Build At the top, there’s an Automation Start block, which begins the sequence. By clicking “+”, a menu with available automation functions opens. ​ Send Connection Request In the “Send Connection Request” settings window, you’ll find a connection note field (1) - can be left blank, or you can add a short personalized message: up to 300 characters for LinkedIn Premium accounts, or up to 200 characters for non-premium accounts. ​ We recommend keeping the switch “Skip note if limit reached” (2) turned on, so the system continues sending connection requests without personalization once the limit is reached (important for non-premium accounts, which currently have a limit of up to 5 personalized requests per month). ​ A built-in option to set a delay before execution (3). Example: if you set 3 days, the request will be sent only after 3 days, not immediately. Withdraw Connection Request Automatically withdraws unanswered requests. ​ Send Message In the modal window, the following functionality is available: 1 - Text field for the message. 2 - Option to attach files. 3 - Use of variables for personalization (30+ default variables available; custom variables can also be created). Learn more here. 4 - Toggle - Send always: - When off, automation stops if the lead replies. - When on, messages will still be sent even if a reply was received. Send Email 1 - Choose which email to send to: personal, work, or both. 2 - Send in previous thread - keep on if you want all emails to appear in the same thread (subject must remain the same). Turn off if you plan to use different subjects. 3 - Use template - allows you to apply pre-made email templates. 4 - Subject field. 5 - Email body field. Social Nodes The main goal of this section is to increase your visibility to potential clients. It is typically used between message sequences or before sending a connection request. Available actions include visiting profiles, liking and commenting on posts, and endorsing skills. Key points to consider: - LinkedIn tracks profile visit frequency, so avoid excessive use of the visit profile function. - for post comments, you can write a custom template, but keep in mind that the system will comment on the latest post without analyzing its content. To avoid issues, use a neutral comment that fits any type of post. - skill endorsements are only available for 1st-degree connections, so apply this function only after your connection request has been accepted. ​ Rotate Sender Profile switches to another sender profile, forcing the contact to go through the sequence again (often used when a request remains unaccepted for a long time). Learn more in this article. ​ A/B test splits the sequence into branches with different actions. You can adjust both the number of branches and the distribution percentage. ​ ​​Condition Rules filter contacts to create different scenarios. ​ ​​Time Delay add a delay after any action. End Automation ends the sequence. Triggers Wait for Connection - this trigger is essential after sending a connection request, as it determines whether the request was accepted and helps structure the message flow accordingly. Wait for Reply (any channel) - checks whether the lead has responded to your message. ​ Both triggers support Social Activity actions and wait time settings. They can be set sequentially throughout the automation. ​ *Common mistake – setting a trigger for only 1 day. Keep in mind that the trigger will only be active for the duration you specify. If the connection request trigger is set to 1 day, any lead who doesn’t accept within 24 hours will move down the "No Connect" path. Even if they accept later, they won’t return to the trigger stage. To prevent this, set the connection request trigger to 14–20 days and the message reply trigger to at least 3–4 days between messages. ​Add Tag automatically adds a tag. ​ Remove Tag removes a tag. ​ Change List ​moves contacts to another folder. Change Pipeline Stage ​changes pipeline stage. Change Sender Profile switches the active sender profile mid-sequence. Call Custom Webhook, Call API allows integrations with external tools (requires prior setup). Detailed guide: Webhook & API Call. ​ 2. Add Sender Profiles Here, select one or multiple sender profiles (1) that will be used in the automation. If multiple, configure the distribution logic (2) between them. More info about methods of distribution here. ​ If no sender profiles exist yet, you can create them directly here via "Create Sender Profile" (3). More info about creating and connecting a sender profile here. 3. Add Contacts Click Add Contacts. ​ The system offers 4 options: - Import existing CRM contacts. - Create a new dedicated import using: Basic Search, Sales Navigator Search, or CSV file. Learn more about imports here. 4. Launch Final setup before launch: 1 - Choose a name for the automation. 2 - Optionally assign a folder. 3 - Set priority. 4 - Configure the schedule if necessary. ​ By default, the switch “Use Sender Profile’s Schedule” is on, meaning automation follows the sender’s schedule. You can override it, but remember the server's schedule must align with the automation schedule. Otherwise, the automation may not function correctly or at all. More info about sender profile work schedule. ​ 5 - Click "Launch" and your automation will start.

Last updated on Jul 02, 2026

Editing an Active Automation: Key Things to Know

While editing an active automation, it’s important to understand that certain types of changes may lead to logical errors in its execution. In this guide, we’ll review the most common types of edits and their potential consequences within the automation flow. ​ The core principle of automation logic is the “waterfall” structure. A contact begins its journey from the very top (the Segment block) and moves downwards through the defined path, executing tasks in the specified order. If a contact has already progressed past a certain point in the flow, it will not be affected by changes made to any blocks above that point. Adding a Sender Profile to an Active Automation Once automation is launched for the first time, the system immediately begins distributing uploaded contacts across the existing sender profiles. Each contact is linked to a specific sender profile and, under standard conditions, does not switch profiles later. Therefore, if a new sender profile is added to an active automation, contacts uploaded prior to this addition will not see the new profile and will continue performing actions assigned based on the original distribution. However, new contacts added after the sender profile is linked will be distributed among all available profiles. You can still manually redistribute previously uploaded contacts. To do this, you need to set the distribution type of the sender profile block to 'Random Rotation'. Use the “Restart from Top” function to restart all 'In Progress' contacts from your chosen node. More details on distribution types and restarting contacts can be found in this manual. Note: We recommend not restarting contacts that have already moved past the Send Connection Request step. Instead, focus on redistributing only those contacts that haven’t yet completed key actions, such as sending a connection request. Removing a Sender Profile from an Active Automation When a sender profile is removed from an active automation, the system will prompt you to choose one of two actions: - Cancel tasks for this profile: all actions linked to this sender profile in the automation will be cancelled. - Keep tasks active: no new contacts will be assigned to this profile, but existing contacts already linked to it will complete all planned tasks. ## Editing Existing Steps or Adding New Steps in an Active Automation Due to the waterfall logic, contacts that have already progressed deeper into the automation will not recognize any new node that was added above their current step. In contrast, new contacts added later will follow the updated path, including the new step. Example: If you add a Visit Profile node above step #2 (Send Connection Request), contacts in step #2 with 'In Progress' status will be able to execute the Visit Profile action. However, contacts already in step #6 (Connection Request Accepted) will not see or execute this new step, as they have moved further down the flow. Deleting Steps in Active Automation When any node is deleted from an automation, all contacts with 'In Progress' status at that node will lose their reference point. As a result, these contacts will be marked as Cancelled or Failed and will not continue along the automation path.

Last updated on Jul 02, 2026

Setting up "Rotate Sender Profile" function

A new feature has recently been added to automations - the ability to rotate sender profiles in a closed-loop manner. How does it work, and how is it different from “Change Sender Profile” or “Send to Another Automation”? The "Change Sender Profile" node allows you to assign a new sender profile, after which you need to build a separate sequence for that new sender - this assumes the logic for that sender might be completely different. The "Send to Another Automation" node simply sends the contact to a completely different campaign, where an entirely new sequence may apply. The new "Rotate Sender Profile" function, on the other hand, sends the contact back to the top of the same automation, assigns a new sender profile, and allows the contact to go through the same sequence again - but with a different sender. Here is an example use case: a contact receives a connection request. If it’s not accepted within 10 days, the contact goes back to the start of the sequence, the sender profile changes, and another profile tries to send the connection request again. ​ How to set up the “Rotate Sender Profile” node When selecting sender profiles for your automation, make sure to choose the distribution method “Rotate to a new Sender Profile.” This ensures that during each rotation, the contact won’t be sent to a sender who has already interacted with them in this campaign. Select the Segment(1) in the segment field, where the contact should be restarted from. ​Choose a specific Sender Profile(2) to route the contact to. You can select any profile here - even one that isn’t directly connected to the automation. *If left this field empty, the platform will automatically assign a profile from the connected ones within the selected segment. The Add Rotation (3) button adds a new rotation cycle. For example, if you create 3 rotations, the node will attempt to change the sender profile up to 3 times, unless stopped earlier by automation rules or sequences. Important to note: If your automation continues below the Rotate Sender Profile node (as shown in the screenshot), the contact will only move to the next node (e.g., Withdraw Connection Request) after all planned rotation cycles are completed. The action will be executed only by the last assigned sender profile. What happens if there are more rotations than sender profiles? If you did not specify a particular sender in the node settings, and there are no remaining unused sender profiles in the segment, the contact will receive a "Failed" status once all options are exhausted. Automation will stop for those contacts. *This behavior only applies if the sender profile distribution method is set to “Rotate to a new Sender Profile.” Other distribution methods may risk assigning the same contact to the same profile more than once.

Last updated on Jul 02, 2026

How to Create a Webhook?

To create a webhook, go to Settings on the left sidebar, select the Webhooks section, and click the "Create webhook" button. Next, you need to give your webhook a name and select an event from the list to which the webhook will respond. *The event "Contact Exported" may not be obvious—this is a semi-manual Webhook that allows you to export leads from the CRM in just one click. Now, go to make.com (used as an example, but you can choose any service that suits you) and “create a new scenario”: Select Webhooks ⇒ Custom Webhooks Once the Webhook is created, copy the generated link. Return to Grinfi Sales, paste the copied link into the Target URL field, and click "Create." That's it! The Webhook has been created on our side. ​ To receive data, follow these steps: go back to make.com and click "Save." ⇒ run it once ⇒ return to Grinfi, click on the created Webhook, then click "…" ⇒ select "Test", pick a contact for testing, and confirm. Now, check make.com—you’ll see that the Webhook has successfully received all contact details, including position, company, etc. At this stage, you can configure the Webhook to suit your needs. For example, you’d like to send the data to Google Sheets or into a CRM. To do this, create the second part of the Webhook (1), linking it to the system where you want to export data. Then, configure it according to the provider’s documentation, selecting which data you want to export (2).

Last updated on Jul 02, 2026