RuCaptha settings

Connecting RuCaptcha to Afina

A wide list of automation scenarios in Afina demands captcha recognition support. Furthermore, the platform delivers seamless captcha solving through a single integration with the RuCaptcha service. The result is brilliant for any script flow that sends a captcha image for recognition and waits for the answer before resuming execution.

Benefits of the RuCaptcha Integration

• Reliable Captcha Solving: RuCaptcha's solving engine is totally effective for any automation pipeline.
• Centralized Token Storage: A user keeps the credential in one global variable. Thus, every script reaches the same value without duplication.
• Easy Maintenance: When credentials need replacement, an update in one location is enough. So, every scenario picks up the new value automatically.
• Smooth Script Execution: Scripts run without interruption while RuCaptcha handles the captcha workload in the background.

Getting a Service Key

First, register on rucaptcha.com. Top up the balance. Copy the credential from the service account dashboard. The dashboard delivers quick visibility into balance details, key management, and usage statistics.

Adding the Credential to Afina

Once the credential is on hand, the next move is registering it inside Afina as a global value. The platform supports a wide list of global variables for various integrations. Users can create or edit a variable with the following name:

__rucaptcha__api__

The value of this variable is exactly the credential received from the RuCaptcha service. Furthermore, the variable becomes available across the platform once it is saved.

After saving, Afina is fully ready to use this credential in components related to captcha recognition.

Using It in Scripts

Once __rucaptcha__api__ is configured, it can be referenced in any script where captcha handling is required. The best part of this design is that a user does not enter the credential manually in every scenario. Instead, the value is stored centrally and reused across all scripts.

Moreover, this design simplifies script maintenance for any business size. When credentials need replacement, an update in one location is enough. Thus, every scenario picks up the new value without manual intervention.

Important

Before running any scripts, users must verify that the RuCaptcha balance is topped up and the credential is entered without errors. The positive part is any balance issue is easily monitored through the RuCaptcha dashboard.

Furthermore, the credential must not be shared with third-party users under any circumstances. On the other hand, if the value was accidentally published or shared with another person, users should replace it inside the RuCaptcha account dashboard and update the __rucaptcha__api__ value in Afina.